Glassfish V3 lookup exception

[Rentius Engelbrecht]

Hi Everyone

We've separated our war from the ejb. They are on different servers and deployed on glassfish V3.1 build 43.

When we try to do an remote lookup to the ejb from the war we get the following error:

javax.naming.CommunicationException: Communication exception for SerialContext[myEnv={org.omg.CORBA.ORBInitialPort=49254, java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory, org.omg.CORBA.ORBInitialHost=10.0.0.***, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming} [Root exception is java.lang.SecurityException: Credential list size is not 1.]

                at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:542)

                at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)

                at javax.naming.InitialContext.lookup(InitialContext.java:392)

                at javax.naming.InitialContext.lookup(InitialContext.java:392)

                at za.co.kineto.utils.FacadeLookup.lookupSystemFascadeRemote(FacadeLookup.java:241)

                at za.co.kineto.aam.util.StanleyGeneratorUtil.generate(StanleyGeneratorUtil.java:17)

                at za.co.kineto.aam.quartz.DebitOrderJob.execute(DebitOrderJob.java:77)

                at org.quartz.core.JobRunShell.run(JobRunShell.java:199)

                at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)

Caused by: java.lang.SecurityException: Credential list size is not 1.

                at com.sun.enterprise.iiop.security.SecClientRequestInterceptor.getCred(SecClientRequestInterceptor.java:145)

                at com.sun.enterprise.iiop.security.SecClientRequestInterceptor.send_request(SecClientRequestInterceptor.java:321)

Anybody got an idea what might cause the error? Played around with the IIOP listener setting and been searching on the internet but got nothing.

We have multiple apps connecting(lookup) to the ejb's.

Kind regards

Rentius 

[Carl Woermann]

Just a guess -

Maybe check whether the versions of java are the same (vendor and version) on both boxes - it could be a case of one jvm attempting to make a secure connection to another version - most newer linux distros ship with java versions other than sun/ oracle, and for some reason the security stuffs seems to fail.  ( in our case its rmi, not corba nd our webstart rmi calls only work with the sun/ oracle version).

good luck
Carl

--
You received this message because you are subscribed to the Google Groups "CTJUG Forum" group.
To post to this group, send email to CTJUG...@googlegroups.com
To unsubscribe from this group, send email to CTJUG-Forum...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/CTJUG-Forum
For the ctjug home page see http://www.ctjug.org.za
For jobs see http://jobs.gamatam.com/

[Rentius Engelbrecht]

Hi Carl, thank you for the response.

I've checked and they run on the same version of Windows 2008 R2 Version 6.1 Build 7600 and java 1.6.0_26-b03. 

The windows and java is 64bit and they are hosted on vmware virtual machines.

I'm not sure what may be causing the issue. On Glassfish V2 it worked flawlessly.

Kind regards

Rentius

[Carl Woermann]

Ok -- i have no experience with windows... but I wonder if you should check how your war deployment knows where to find the server it is connecting to. I hav'nt done any ejb dev in years so I'm lost as to the current state of deployment options...

[Bruce Stewart]

The root cause appears to be a security issue. What sort of security settings are you using?

Did you find this in your googling?  http://www.java.net/forum/topic/glassfish/glassfish/remote-ejb-call-problem 

[Rentius Engelbrecht]

Hi Bruce

Thanks. 

Yes, got the link when I googled for the issue.

Trying to setup it the same way, but not 100% sure how to setup security correctly for the lookups and on glassfish V3.

Also getting the following error while trying to sort out the credential list error. This exception actually happens on startup before the credential list size exception.

javax.enterprise.resource.corba.org.glassfish.enterprise.iiop.impl|_ThreadID=100;_ThreadName=Thread-1;|enterprise_util.excep_in_createorb

java.lang.IllegalStateException: Invalid iiop-listener orb-listener-1. Lazy-init not supported for SSL iiop-listeners

The top exception is a known issue:

http://docs.oracle.com/cd/E18930_01/html/821-2434/ggrvi.html#gkwxs

When we follow the workaround we get the credential list size not 1 security exception

Regards

Rentius