Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

connecting to weblogic 4.5.1  RSS feed

 
seetarama raju
Ranch Hand
Posts: 104
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
recently i have a problem in my project. previously i was hitting weblogic server 6.1 from
a simple java program. it used to work fine. they have now changed it to weblogic 4.5, it is started giving an error saying java.lang.verify error -- incomaptable object argument for function call. i've included all the class path statements
and running a main which connects to weblogic.
it seems it is finding all the required jar files,
but missing on some verification. can somebody help me out with this.
thanks in advance
 
Dave Landers
Ranch Hand
Posts: 401
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just a guess - maybe you have the version 6 weblogic.jar in your client's classpath? Switch that out for the weblogic.jar from 4.5.1. And you might need to recompile your client against the 4.5.1 jar.
 
seetarama raju
Ranch Hand
Posts: 104
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i've tried that. but one doubt i've is, do we need to use environment instead of properties object while setting the initial context. can somebody elaborate on this please.
 
seetarama raju
Ranch Hand
Posts: 104
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
the following is the complete stack trace iam getting
java.lang.VerifyError: (class: weblogic/kernel/ExecuteThread, method: execute signature: (Lweblogic/kernel/ExecuteRequ
at weblogic.kernel.ExecuteThreadManager.setThreadCount(ExecuteThreadManager.java:91)
at weblogic.kernel.ExecuteThreadManager.<init>(ExecuteThreadManager.java:48)
at weblogic.kernel.Kernel.addExecuteQueue(Kernel.java:310)
at weblogic.kernel.Kernel.initialize(Kernel.java:124)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:83)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:163)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at com.strong.crd.domain.common.CRDRTPHelpertest.getPrice(CRDRTPHelpertest.java:84)
at com.strong.crd.domain.common.CRDRTPHelpertest.getRTPPrice(CRDRTPHelpertest.java:32)
at com.strong.crd.domain.common.testRTPloader.main(testRTPloader.java:29)
Exception in thread "main" java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:86)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:163)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
 
seetarama raju
Ranch Hand
Posts: 104
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i would like to specify one more thing. the jar file iam using for weblogic 4.5 doesn't contain wlinitial context factory class. for this iam
using the weblogic 6.0 jar file. what should i do for this.
 
Dave Landers
Ranch Hand
Posts: 401
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you have any part of the weblogic.jar for 6.x in your classpath, that is why you are getting the veriry error. Don't do that.
Check the weblogic docs for 4.5.1 to find out how to do jndi -
http://www.weblogic.com/docs45/classdocs/API_jndi.html
Also, if I remember, in 4.5.1 you had to set both classpath and weblogic.class.path correctly. And there was not a weblogic.jar, but classes directories. Again read the docs about classpath -
http://www.weblogic.com/docs45/admindocs/classpath.html
 
seetarama raju
Ranch Hand
Posts: 104
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i got over this problem. but now iam facing another problem while looking up the home interface. even though i've the client jar file
in the classpath, it is giving a no class found
exception for the home interface's stub class.
can somebody help me with this
thanks
 
Dave Landers
Ranch Hand
Posts: 401
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It has been a long time since I work with WLS 4.5.1, but I think you had to have the stub classes available to your client (in client jar).
So all those output from ejbc have to be there.
Easiest thing to try is put the entire ejb jar in the client classpath. Then, if that works you can work on removing classes that you don't need and make a real client jar.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!