Communication Channel Error.

[Former Member]

Hi all,

Currently we are using XI 7.0,

For two of the communication channels with adapter type JMS, we are getting an error,

for the first one, error message is,

Error during channel initialization; exception trace: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://mvwsdv07:7010: Destination unreachable; nested exception is:

java.net.ConnectException: Connection refused: connect; No available router to destination]

at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)

at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:636)

at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)

...

for the second, error message is,

Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:243)

at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)

at com.sap.engine.system.naming.provider.DefaultInitialContext.(DefaultInitialContext.java:46)

at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

at javax.naming.InitialContext.init(InitialContext.java:219)

at javax.naming.InitialContext.(InitialContext.java:195)

at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:318)

at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:124)

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]

at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)

... 13 more

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.

at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:180)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:172)

at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)

... 14 more

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.

at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)

... 17 more

Please suggest as to how to go about resolving this problem.

Thanks,

vishnu.

[Former Member]

Hi,

your first JMS adapter is erroring because your JMS server is either not running or there is some firewall issue because of which XI server is not able to connect to your JMS server................

for the second JMS adapter, i think the user you have used in your this JMS comm channel configuration in ID does not has authorization to connect to your JMS server........

Regards,

Rajeev Gupta

[Former Member]

Hi Rajeev,

For the first Comm channel, How do we check if the JMS server is running or not?

For the second comm channel, what authorizations would be necessary.

Really Appreciate your help.

Thanks,

vishnu.

Edited by: vishnuarigela on Feb 5, 2009 9:29 AM

Edited by: vishnuarigela on Feb 5, 2009 10:34 AM

[former_member200962]

Hi,

In JMS adapter you have a field called JMS Queue user and JMS Queue Password......make sure that you have entered the necessary details here....This user is necessary to access the JMS queue....if not specified then access will be denied..

for more information refer:

http://help.sap.com/saphelp_nw70/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm

Regards,

Abhishek.

[Former Member]

Hi Abhishek,

How do I find the JMS Queue User name and password? Should the user define them when creating a queue, if Yes, how do I do it? If not, which Username and password should I use there?

Thanks,

vishnu vardhan.

[former_member200962]

Hi,

you can check with the person who assigned you this development...he might be knowing the details....the user-id will be assigned with the right to access JMS queue.....if not critical/ confidential scenario then you can ask the admin to assign your XI-id with the permission to access the JMS queue and then update these details (your XI-id and password) in the channel.

Regards,

Abhishek.

[Former Member]

Hi all,

Thank you very much for your answers.

I have another question regarding the same problem.

Instead of using Access JMS provider with JNDI as Transport Protocol,

if we use WebSphereMQ(MQSeries) JMS provider, it is my understanding

that we need to install WebSphereMQ series and the related .jar files.

Is the WebSphereMQ series part of WebSphere Application Server,

or is it a separate installation? Would it be necessary to install

the entire WebSphere Application Server for WebSphere MQ Series?

Thanks,

vishnu.

[Former Member]

Hi,

Instead of using Access JMS provider with JNDI as Transport Protocol,

if we use WebSphereMQ(MQSeries) JMS provider, it is my understanding

that we need to install WebSphereMQ series and the related .jar files. - Yes but you will use WebSphereMQ(MQSeries) JMS provider for connection of your XI sevr to your WebSphereMQ series server.

Regards,

Rajeev Gupta

[Former Member]

Hi Rajeev,

Could you clarify this question as well for me.

Is the WebSphereMQ series part of WebSphere Application Server,

or is it a separate installation? Would it be necessary to install

the entire WebSphere Application Server for WebSphere MQ Series?

Thanks,

vishnu.

[Former Member]

Hi,

Is the WebSphereMQ series part of WebSphere Application Server, or is it a separate installation? - Websphere MQ is a separate software.

Would it be necessary to install the entire WebSphere Application Server for WebSphere MQ Series? - You will have to install WebSphere MQ for Websphere mqseries.

Regards,

Rajeev Gupta

[rajasekhar_reddy14]

Check in Visual Admin, you configured drivers properly or not,

then check you using corect JMS Queues.

[madanmohan_agrawal]

Check if JMS driver is installed correctly or not.

[Former Member]

Hi Madan,

The transport protocol that we are using is Access JMS provider with JNDI

Should we install drivers for this separetely. If yes, where can I find them.

Really Appreciate your help.

Thanks,

vishnu.

Edited by: vishnuarigela on Feb 5, 2009 9:31 AM