This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Websphere and the fly likes Writing to a topic on remote system Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Writing to a topic on remote system" Watch "Writing to a topic on remote system" New topic
Author

Writing to a topic on remote system

prashanth
Greenhorn

Joined: Jan 18, 2006
Posts: 1
Hi,
The client application and also the JMS application are running on websphere 6 and on different systems.The client application is trying to write to a Topic which has been configured in JMS application.When the client application tries to fetch the TopicConnectionFactory,the following error occurs:
NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
Exception stack trace: javax.naming.NamingException: Error during resolve. Root exception is java.lang.NullPointerException
at com.ibm.ISecurityLocalObjectBaseL13Impl.CSICredentialsManager.getClientSubject(CSICredentialsManager.java:389)
at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientRI$2.run(CSIClientRI.java:463)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIClientRI.send_request(CSIClientRI.java:459)
at com.ibm.rmi.pi.InterceptorManager.iterateSendRequest(InterceptorManager.java:396)
at com.ibm.rmi.iiop.ClientRequestImpl.<init>(ClientRequestImpl.java:136)
at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.java:141)
at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.java:97)
at com.ibm.rmi.corba.ClientDelegate._createRequest(ClientDelegate.java:1899)
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1177)
at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1285)
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1110)
at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1251)
at com.ibm.rmi.corba.ClientDelegate.request(ClientDelegate.java:1776)
at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDelegate.java:1207)
at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:460)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4045)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1776)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1324)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at org.apache.log4j.net.JMSAppender.lookup(JMSAppender.java:237)
at org.apache.log4j.net.JMSAppender.activateOptions(JMSAppender.java:205)
at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:123)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:87)
at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:645)
at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:603)
at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:500)
at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:406)
at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:307)
at org.apache.log4j.PropertyWatchdog.doOnChange(PropertyConfigurator.java:673)
at org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:80)
at org.apache.log4j.helpers.FileWatchdog.<init>(FileWatchdog.java:49)
at org.apache.log4j.PropertyWatchdog.<init>(PropertyConfigurator.java:665)
at org.apache.log4j.PropertyConfigurator.configureAndWatch(PropertyConfigurator.java:373)
at com.misys.equation.common.logger.Log4jLogger.init(Log4jLogger.java:105)
at com.misys.equation.common.logger.Log4jLogger.<init>(Log4jLogger.java:48)
at com.misys.equation.common.logger.LogFactory.newLogger(LogFactory.java:20)
at com.misys.equation.batch.framework.ejb.mdb.NotificationListenerBean.<clinit>(NotificationListenerBean.java:54)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java(Compiled Code))
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java(Compiled Code))
at java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled Code))
at java.lang.Class.newInstance3(Class.java(Compiled Code))
at java.lang.Class.newInstance(Class.java(Compiled Code))
at com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1596)
at com.ibm.ejs.container.HomeOfHomes.loadBeanMetaData(HomeOfHomes.java:659)
at com.ibm.ejs.container.HomeRecord.getHomeAndInitialize(HomeRecord.java:458)
at com.ibm.ejs.container.EJSContainer.getHomeWrapperCommon(EJSContainer.java:1236)
at com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.java:1145)
at com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:1131)
at com.ibm.ws.runtime.component.EJBContainerImpl.startBean(EJBContainerImpl.java:3212)
at com.ibm.ws.runtime.component.EJBContainerImpl.install(EJBContainerImpl.java:2684)
at com.ibm.ws.runtime.component.EJBContainerImpl.start(EJBContainerImpl.java:3419)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1019)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1028)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:538)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:724)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:683)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:1678)
at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)


I have enabled Global security on both instances of Websphere.Please help me to solve this problem.
Marc Peabody
pie sneak
Sheriff

Joined: Feb 05, 2003
Posts: 4727

"java prash ", welcome to the ranch. Please take a few moments to read the Javaranch naming policy. We try to be friendly around here but we do have our rules, and not following the naming policy can result in having your account deleted.

We'd prefer to keep you with us.


A good workman is known by his tools.
Pat Spatola
Greenhorn

Joined: Mar 08, 2006
Posts: 1
Did you ever get an answer to this problem
Frank Zoontjens
Greenhorn

Joined: Jul 21, 2004
Posts: 2
I am getting the same NullPointerException on Websphere 5.1.1.11, when a Java client uses an EJB from within a WSSubject, on server1, and this EJB in its turn tries use the JNDI context of server2.

Did you manage to solve this?
Frank Zoontjens
Greenhorn

Joined: Jul 21, 2004
Posts: 2
Solved it myself.

It is a bug in SWAM authentication mechanism of Websphere in SAS when the credentials are passed on just before where the nullpointerexception occurs. When I turned it to LPTA it disappeared, and also, seemed to be much faster.

Frank
 
jQuery in Action, 2nd edition
 
subject: Writing to a topic on remote system
 
Similar Threads
JNDI exception.
Could not read configuration file [log4j.properties].
J2CXAResource E J2CA0036E: Error in WSAD v5.0
JMX Implementation In WAS
Websphere 5.0 : EJB Naming exception : Urgent