RMI problem with weblogic.jar
We have a pure Java client that connects to the Weblogic server.
While trying to connect we receive the error message below.
I have unjarred the weblogic.jar file and discovered that the
Stub.class is actually in weblogic/rmi/extensions/server/
while it expects it to be in weblogic/rmi/extensions .
Is there a fix for this as we are trying to upgrade from a previous version of weblogic and go live in Jan.
Thanks
Dave F
java.lang.NoClassDefFoundError: weblogic/rmi/extensions/Stub(
I'd suggest that you run the vm with the debug flag (-verbose) and see where the classes are being loaded; and examine the classpath to determine where the old jar or classes are occurring.
Rita wrote:
We have re-jarred the Stub.class and put it under weblogic/rmi/extensions, but when the java app runs, it still tries to look in weblogic/rmi/extensions/server. So, I think somewhere in the weblogic.jar, the path specified is still weblogic/rmi/extensions. Do you know what need to be done?
Thanks,
Rita
Eduardo Ceballos <[email protected]> wrote:
Yes, please regenerate your stub classes. That is, re-run rmic or ejbc.
David Furlong wrote:
We have a pure Java client that connects to the Weblogic server.
While trying to connect we receive the error message below.
I have unjarred the weblogic.jar file and discovered that the
Stub.class is actually in weblogic/rmi/extensions/server/
while it expects it to be in weblogic/rmi/extensions .
Is there a fix for this as we are trying to upgrade from a previous version of weblogic and go live in Jan.
Thanks
Dave F
java.lang.NoClassDefFoundError: weblogic/rmi/extensions/Stub(
Similar Messages
-
Problem with protocol.jar with weblogic
atg10.0.3 and weblogic 11g on 64bit linux.
I've been plagued by this problem with ATG's protocol jar. While it loads the jar when starting up startWeblogic.sh it does not get loaded when starting a managed server thus i get the following errors:
**** Error Fri Jun 15 15:56:43 MDT 2012 1339797403444 / Unable to start service "/atg/scenario/ScenarioManager": atg.nucleus.ServiceException: The configuration file XMLFile(/atg/scenario/scenarioManager.xml) could not be read: java.net.MalformedURLException: unknown protocol: dynamosystemresource
**** Error Fri Jun 15 15:56:43 MDT 2012 1339797403544 /atg/scenario/ScenarioManager Unable to combine messaging information from the process manager component /atg/scenario/ScenarioManager. The process manager has not been classified yet so it cannot be determined if global messages should be listened for. This error indicates a problem with component startup order - the /atg/scenario/ScenarioManager component has been started before the /atg/dynamo/messaging/MessagingManager component
**** Error Fri Jun 15 15:56:43 MDT 2012 1339797403583 /atg/dynamo/messaging/MessagingManager An exception occurred while trying to parse XML definition file "XMLFile(/atg/dynamo/messaging/dynamoMessagingSystem.xml)" java.net.MalformedURLException: unknown protocol: dynamosystemresource
Following instructions has led me to place the protocol.jar from DAS/lib to the root of my domain directory and then apply the classpath entry in startWeblogic.sh script. protocol.jar shows up at the top of this scripts SDTOUT. But I cannot seem to get it included in the production.out logs when starting the managed server.
Any ideas?
Thanks!
-KipYes I figured this out. The problem was the version of weblogic. I was using 1.3.6 when it should have been 1.3.5. After changing out the version, I no longer had problems with protocol.jar.
Thanks!
-Kip -
Problem with Weblogic Builder SP1
I have a problem with Weblogic Builder SP1. I basically re-used my EJB deployment
descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loading my EJB
in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
I re-attempted by jarring my EJB with WL5.1 descriptors and used my friend's WB
(not SP1) to export new descriptors which I used to re-jar. This new EJB is again
not recognised by WB SP1?
What is wrong?The exception is as follows:
Opening module myproj.jar
java.lang.NullPointerException
at java.util.Arrays.sort(Arrays.java:1181)
at weblogic.marathon.model.EJBJarCMBean.initRelations(EJBJarCMBean.java:1212)
at weblogic.marathon.model.EJBJarCMBean.initBeans(EJBJarCMBean.java:1098)
at weblogic.marathon.model.EJBJarCMBean.setup(EJBJarCMBean.java:1144)
at weblogic.marathon.tasks.OpenModuleTask.getEJBModule(OpenModuleTask.java:156)
at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:191)
at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:230)
at weblogic.marathon.tasks.OpenModuleTask.runBackground(OpenModuleTask.java:89)
at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127)
at weblogic.tools.jellybeans.core.task.TaskThread.run(TaskThread.java:64)
Module myproj.jar descriptors failed to load
The EJB has no problem deploying.
Rob Woollen <[email protected]> wrote:
You'll have to at least show us the error you get from marathon.
Does your application deploy to the server?
-- Rob
Robin Tan wrote:
I have a problem with Weblogic Builder SP1. I basically re-used myEJB deployment
descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loadingmy EJB
in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
I re-attempted by jarring my EJB with WL5.1 descriptors and used myfriend's WB
(not SP1) to export new descriptors which I used to re-jar. This newEJB is again
not recognised by WB SP1?
What is wrong? -
Problem with weblogic.Deployer in 8.1
I have a problem with weblogic.Deployer. My application deploys and works fine
if I manually copy the ear or the exploded form into weblogic's applications\
directory (hot deployment). But, if I use the weblogic.Deployer tool, it fails
with the following exception. Does the deployer tool expect something in the ear
(or exploded form) that I'm missing? Thanks in advance.
-Vas
[wldeploy] java.lang.NullPointerException
[wldeploy] at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGener
ator.java:785)
[wldeploy] at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerato
r.java:758)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:803)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] --------------- nested within: ------------------
[wldeploy] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed
to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub ]
with nested exception:
[wldeploy] [java.lang.NullPointerException]
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:807)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] java.lang.reflect.InvocationTargetException
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] Caused by: weblogic.utils.AssertionError: ***** ASSERTION FAILED ***
**[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811
_WLStub ] - with nested exception:
[wldeploy] [java.lang.NullPointerException]
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:807)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] ... 15 moreHi Deepak,
I didn't understand the suggested resolution. Can you tell me what it means?
However, I found a similar problem in the archives, so I tried from command line
(outside ant) using "java weblogic.Delployer ...." and it worked! It doesn't work
from ant. So, you think there's some conflict between my ant and weblogic's ant
task "WLDdeploy"?
Thanks,
Vas
"Deepak Vohra" <[email protected]> wrote:
>
Refer to
http://e-docs.bea.com/wls/docs70/notes/resolved.html#1296363
"vas pulipati" <[email protected]> wrote:
I have a problem with weblogic.Deployer. My application deploys andworks
fine
if I manually copy the ear or the exploded form into weblogic's applications\
directory (hot deployment). But, if I use the weblogic.Deployer tool,
it fails
with the following exception. Does the deployer tool expect something
in the ear
(or exploded form) that I'm missing? Thanks in advance.
-Vas
[wldeploy] java.lang.NullPointerException
[wldeploy] at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGener
ator.java:785)
[wldeploy] at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerato
r.java:758)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:803)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] --------------- nested within: ------------------
[wldeploy] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Failed
to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub
with nested exception:
[wldeploy] [java.lang.NullPointerException]
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:807)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] java.lang.reflect.InvocationTargetException
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
.java:209)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
va:170)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
va:166)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
[wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
[wldeploy] Caused by: weblogic.utils.AssertionError: ***** ASSERTION
FAILED ***
**[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811
_WLStub ] - with nested exception:
[wldeploy] [java.lang.NullPointerException]
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:807)
[wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
r.java:790)
[wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
79)
[wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
rviceStub.java:50)
[wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
.java:152)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
otely(WLInitialContextFactoryDelegate.java:597)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
nitialContextFactoryDelegate.java:534)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
itialContextFactoryDelegate.java:336)
[wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
xt(WLInitialContextFactoryDelegate.java:308)
[wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
[wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
143)
[wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
BeanHomeTool.java:157)
[wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[wldeploy] at weblogic.Deployer.main(Deployer.java:399)
[wldeploy] ... 15 more -
Performance problem with ojdbc14.jar
Hi,
We are having performance problem with ojdbc14.jar in selecting and updating (batch updates) entries in a table. The queries are taking minutes to execute. The same java code works fine with classes12.zip ans queries taking sub seconds to execute.
We have Oracle 9.2.0.5 Database Server and I have downloaded the ojdbc14.jar from Oracle site for the same. Tried executing the java code from windows 2000, Sun Solaris and Opteron machines and having the same problem.
Does any one know a solution to this problem? I also tried ojdbc14.jar meant for Oracle 10g, that did not help.
Please help.
Thanks
YuvaMy code is doing some thing which might be working well with classes12.zip and which does not work well with ojdbc14.jar? Any general suggestions to make the code better, especially for batch updates.
But for selecting a row from the table, I am using index columns in the where cluase. In the code using PreparedStatement, setting all the reuired fields. Here is the code. We have a huge index with 14 fields!!. All the parameters are for where clause.
if(longCallPStmt == null) {
longCallPStmt = conn.prepareStatement(longCallQuery);
log(Level.FINE, "CdrAggLoader: Loading tcdragg entry for "
+GeneralUtility.formatDate(cdrAgg.time_hour, "MM/dd/yy HH"));
longCallPStmt.clearParameters();
longCallPStmt.setInt(1, cdrAgg.iintrunkgroupid);
longCallPStmt.setInt(2, cdrAgg.iouttrunkgroupid);
longCallPStmt.setInt(3, cdrAgg.iintrunkgroupnumber);
longCallPStmt.setInt(4, cdrAgg.iouttrunkgroupnumber);
longCallPStmt.setInt(5, cdrAgg.istateregionid);
longCallPStmt.setTimestamp(6, cdrAgg.time_hour);
longCallPStmt.setInt(7, cdrAgg.icalltreatmentcode);
longCallPStmt.setInt(8, cdrAgg.icompletioncode);
longCallPStmt.setInt(9, cdrAgg.bcallcompleted);
longCallPStmt.setInt(10, cdrAgg.itodid);
longCallPStmt.setInt(11, cdrAgg.iasktodid);
longCallPStmt.setInt(12, cdrAgg.ibidtodid);
longCallPStmt.setInt(13, cdrAgg.iaskzoneid);
longCallPStmt.setInt(14, cdrAgg.ibidzoneid);
rs = longCallPStmt.executeQuery();
if(rs.next()) {
cdr_agg = new CdrAgg(
rs.getInt(1),
rs.getInt(2),
rs.getInt(3),
rs.getInt(4),
rs.getInt(5),
rs.getTimestamp(6),
rs.getInt(7),
rs.getInt(8),
rs.getInt(9),
rs.getInt(10),
rs.getInt(11),
rs.getInt(12),
rs.getInt(13),
rs.getInt(14),
rs.getInt(15),
rs.getInt(16)
}//if
end_time = System.currentTimeMillis();
log(Level.INFO, "CdrAggLoader: Loaded "+((cdr_agg==null)?0:1) + " "
+ GeneralUtility.formatDate(cdrAgg.time_hour, "MM/dd/yy HH")
+" tcdragg entry in "+(end_time - start_time)+" msecs");
} finally {
GeneralUtility.closeResultSet(rs);
GeneralUtility.closeStatement(pstmt);
Why that code works well for classes12.zip (comes back in around 10 msec) and not for ojdbc14.jar (comes back in 6-7 minutes)?
Please advise. -
Problems with weblogic clustering in 6.1 sp3
We have spent a lot of time trying to get our application deployed to
a cluster using weblogic 6.1 sp3 and we consistently receive a failure
when we attempt to start the managed server. This was not a problem
with weblogic sp1--we got our application to deploy to the cluster
successfully; although there was another weblogic bug there with
clients accessing EJB clusters--we won't go into that here...
We have tried this on both a Windows 2000 machine and an HP machine
running weblogic sp3. The same error occurs on both platforms.
The error in deploying our application to the cluster against weblogic
sp3 looks to have to do with our custom security realm. Inside our
custom realm we make use of a configurable providerUrl which we set to
the cluster address/port. The custom realm makes a call where it
passes in the providerUrl to:
weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
When we have our providerUrl set to the cluster address/port--e.g.,
t3://clustermember1:7001
and attempt to start the managed server we get the error:
Starting WebLogic Server ....
Connecting to http://adminserver:7117...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException:
clustermember1 not found
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
at weblogic.management.Admin.initialize(Admin.java:340)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
When we have our providerUrl set to the admin server address--e.g.,
t3://adminserver:7117
everything starts up fine.
Does anyone know why this would work on sp1 and not sp3 of weblogic
6.1?
We verified that all passwords are correct and everything else we
could determine--any ideas would be helpful.
We don't want the providerUrl to point at our admin server, we want it
to point at the cluster address/port.
When we get the managed server error, we received this error on the
AdminServer:
2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
Caught naming exception null; throwing RuntimeException.
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to
destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:307)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
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.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(GabrielRealm.java:416)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRealm.java:347)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.java:51)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:225)
at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(GabrielRealm.java:578)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:221)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
<[WebAppServletContext(8091823,wl_management_internal2,/wl_management_internal2)]
Servlet failed with Exception
java.lang.RuntimeException
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:260)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Thanks for any help.
Rich
Bottom line:
In our custom realm we were not handling user guest correctly. Even if you
have guest user disabled, Weblogic seems to have hard-coded guest to
send messages to the cluster every-so-often. Not sure there--couldn't get
an answer out of bea as to exactly why we see guest still being used...
It seems that with sp3, the user guest interaction started happening earlier
than it did with sp1, consequently making our realm code fail when trying to
retrieve the guest user like someone we knew about in our system.
Hence, our getUser and authUserPassword methods now return null for both
users guest and system, making the secondary realm (file realm) be used to
authenticate and resolve guest & system. BEA helped get our code fixed;
however, we still don't have a lot of depth in understanding Weblogic
server's use of guest...
Apparently, in 7.x the guest & system user behavior and configuration is
different also... We'll see when we start digging into that migration.
Rich
[email protected] (Rich Koch) wrote in message news:<[email protected]>...
> Thanks for the responses--we're working with weblogic support now. We
> think that the custom realm that we have [the developer that wrote it
> left the company] is the problem.
>
> The original developer was told by someone to check:
> weblogic.security.acl.internal.ClusterRealm.THE_ONE != null
>
> In order to determine if the JNDI was available/ready for the whole
> cluster.
>
> It seems that the meaning/setting of THE_ONE changed with this respect
> from
> sp1 to sp3--i.e., this is no longer a valid test to tell us if the
> JNDI is
> ready for the cluster.
>
> We believe this was used because the 'system' user has to be
> authenticated before the custom realm is up. Originally, before this
> check was in place, an exception was received when authenticating
> 'system'. This appears to be a weblogic limitation/issue. Support
> has told us that this is different in weblogic 7.0. Unfortunately, we
> can't upgrade from 6.1 yet.
>
> We'll post the solution when this gets figured out.
>
> Rak
>
> "Sabha" <[email protected]> wrote in message news:<[email protected]>...
> > There was a security restriction enforced from sp2/sp3 onwards in terms of
> > looking up mbeans from admin server.
> >
> > This might cause things to fail if you are attempting to lookup Mbeans with
> > guest priviliges from admin server. Also, can you try doing the following:
> >
> > Run " java weblogic.Admin -url adminServer -username system -password
> > .... -GET -pretty -type Server" and check whether the named clustermember1
> > is available in the list or not.
> >
> > Also you seem to be getting some security exception - can you check that.
> >
> > t3://tomtate.msais.com:7119: Destination
> > unreachable; nested exception is:
> >
> > --- Try running weblogic.Admin PING on this one and see whether you are
> > able to reach this server upon the error message.
> >
> > --Sabha
> >
> > "Rich Koch" <[email protected]> wrote in message
> > news:[email protected]...
> > > We have spent a lot of time trying to get our application deployed to
> > > a cluster using weblogic 6.1 sp3 and we consistently receive a failure
> > > when we attempt to start the managed server. This was not a problem
> > > with weblogic sp1--we got our application to deploy to the cluster
> > > successfully; although there was another weblogic bug there with
> > > clients accessing EJB clusters--we won't go into that here...
> > >
> > > We have tried this on both a Windows 2000 machine and an HP machine
> > > running weblogic sp3. The same error occurs on both platforms.
> > >
> > > The error in deploying our application to the cluster against weblogic
> > > sp3 looks to have to do with our custom security realm. Inside our
> > > custom realm we make use of a configurable providerUrl which we set to
> > > the cluster address/port. The custom realm makes a call where it
> > > passes in the providerUrl to:
> > > weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
> > >
> > > When we have our providerUrl set to the cluster address/port--e.g.,
> > > t3://clustermember1:7001
> > >
> > > and attempt to start the managed server we get the error:
> > >
> > > Starting WebLogic Server ....
> > > Connecting to http://adminserver:7117...
> > >
> ***************************************************************************
> > > The WebLogic Server did not start up properly.
> > > Exception raised:
> > > weblogic.management.configuration.ConfigurationException:
> > > clustermember1 not found
> > > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
> > > at weblogic.management.Admin.initialize(Admin.java:340)
> > > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
> > > at weblogic.Server.main(Server.java:35)
> > > Reason: Fatal initialization exception
> > >
> ***************************************************************************
> > >
> > > When we have our providerUrl set to the admin server address--e.g.,
> > > t3://adminserver:7117
> > >
> > > everything starts up fine.
> > >
> > > Does anyone know why this would work on sp1 and not sp3 of weblogic
> > > 6.1?
> > > We verified that all passwords are correct and everything else we
> > > could determine--any ideas would be helpful.
> > >
> > > We don't want the providerUrl to point at our admin server, we want it
> > > to point at the cluster address/port.
> > >
> > > When we get the managed server error, we received this error on the
> > > AdminServer:
> > >
> > > 2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
> > > 'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
> > > Caught naming exception null; throwing RuntimeException.
> > > javax.naming.CommunicationException. Root exception is
> > > java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
> > > unreachable; nested exception is:
> > > java.net.ConnectException: Connection refused; No available router to
> > > destination
> > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
> > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
> > > at
> > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:307)
> > > at
> > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:211)
> > > at
> > weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
> > ory.java:149)
> > > 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.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(Gabriel
> > Realm.java:416)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRea
> > lm.java:347)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.
> > java:51)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:
> > 225)
> > > at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(Gabriel
> > Realm.java:578)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
> > a:221)
> > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
> > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
> > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
> > > at
> > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
> > ava:356)
> > > at
> > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
> > tSecurityManager.java:205)
> > > at
> > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> > ntext.java:2518)
> > > at
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> > :2260)
> > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> > > <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
> > >
> > <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_intern
> > al2)]
> > > Servlet failed with Exception
> > > java.lang.RuntimeException
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
> > a:260)
> > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
> > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
> > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
> > > at
> > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
> > ava:356)
> > > at
> > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
> > tSecurityManager.java:205)
> > > at
> > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> > ntext.java:2518)
> > > at
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> > :2260)
> > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> > >
> > >
> > > Thanks for any help.
> > >
> > > Rich
-
I am having a problem with signed jar and deploy in html
get this error on the page
self signed
/dist/testfx.html
JavaFX application could not launch due to system configuration. See java.com/javafx for troubleshooting information.Unsigned jar works perfectly but has security and permission issues when using classes.
This was working in beta 45Can you post an example project that demonstrates the problem? There were changes to the ant tasks and netbeans support around B45 that could cause problems depending on which version of the SDK and NetBeans you have. Similarly, if you wrote ant scripts prior to B44 and then use them with a later build you could have problems. And of course, if you're producing the Jar file and deployment artifacts without using the provided ant tasks (for example, using the normal ant jar task) you'll have problems.
I've verified that this works as expected in the FX 2.0 GA release using ant from the command line, and with the NetBeans 7.1 beta release using the FX 2.0 GA release. -
Problem building application with weblogic.jar placed out of bea install.
Weblogic version: 10.3
EJB Version: 2.x
Method for generating webservices fomr EJBs: servicegen task.
Application Build steps:
Step1) Maven to build the complete application and generate ejb-jar.jar and other projects jars and wars.
Step2) Post maven build success there is an ant script used to generate webservices using ejb’s in the project using servicegen task. Attached is build.xml for ant.
Following is the class path :
.;C:\PROGRA~1\IBM\SQLLIB\java\db2java.zip;C:\PROGRA~1\IBM\SQLLIB\java\db2jcc.jar;C:\PROGRA~1\IBM\SQLLIB\java\sqlj.zip;C:\PROGRA~1\IBM\SQLLIB\java\db2jcc_license_cu.jar;C:\PROGRA~1\IBM\SQLLIB\bin;C:\PROGRA~1\IBM\SQLLIB\java\common.jar;C:\Program Files\IBM\RationalSDLC\ClearQuest\cqjni.jar;C:\bea10.3\wlserver_10.3\server\lib\weblogic.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\webservices.jar;%JAVA_HOME%\lib\tools.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\libslf4j-log4j12-1.5.2.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\struts.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\bootstrap.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\db2jcc.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\db2jcc_license_cu.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\ehcache-core-2.0.0.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\j2ee.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\jdom.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\log4j-1.2.9.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\slf4j-api-1.5.8.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\ulc-dto.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\ulc-jar.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\scheduler-ejb.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\com.bea.core.xml.beaxmlbeans_2.0.0.0_2-5-1.jar;
Problem Area:
As you could notice in the yellow highlighted one that am referring to weblogic.jar from bea installation folder. Now if I use the weblogic.jar from the installation folder then build happens successfully.
However if I copy weblogic.jar to some other location say : C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\weblogic.jar
And include this path in the class path in place of weblogic.jar from the installation path, then I get the following errors: Please refer red highlighted part below…
C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\ulc-ear>ant
Buildfile: build.xml
ejbwebservice:
[servicegen] weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed D
OCTYPE header
[servicegen] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:301)
[servicegen] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:241)
[servicegen] at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:320)
[servicegen] at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:295)
[servicegen] at weblogic.ejb20.dd.xml.DDUtils.processEjbJarXML(DDUtils.java:265)
[servicegen] at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:118)
[servicegen] at weblogic.webservice.dd.EJBJarIntrospector.<init>(EJBJarIntrospector.java:47)
[servicegen] at weblogic.webservice.util.WebServiceEarFile.init(WebServiceEarFile.java:177)
[servicegen] at weblogic.webservice.util.WebServiceEarFile.readDD(WebServiceEarFile.java:235)
[servicegen] at weblogic.webservice.util.WebServiceEarFile.<init>(WebServiceEarFile.java:74)
[servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:177)
[servicegen] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[servicegen] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[servicegen] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[servicegen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[servicegen] at java.lang.reflect.Method.invoke(Method.java:597)
[servicegen] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[servicegen] at org.apache.tools.ant.Task.perform(Task.java:348)
[servicegen] at org.apache.tools.ant.Target.execute(Target.java:357)
[servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[servicegen] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[servicegen] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
[servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:758)
[servicegen] at org.apache.tools.ant.Main.startAnt(Main.java:217)
[servicegen] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[servicegen] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
[servicegen] --------------- nested within: ------------------
[servicegen] Error processing file 'META-INF/ejb-jar.xml'. weblogic.xml.process.XMLProcessingException: XML document doe
s not appear to contain a properly formed DOCTYPE header - with nested exception:
[servicegen] [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed
DOCTYPE header]
--------------- nested within: ------------------
weblogic.webservice.util.WebServiceJarException: Could not process ejb-jar C:\DOCUME~1\ac30416\LOCALS~1\Temp\ulc-ear.ear
-86826932\ejb.jar - with nested exception:
[weblogic.webservice.dd.EJBProcessingException: Can read in ejb DD files. - with nested exception:
[Error processing file 'META-INF/ejb-jar.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear
to contain a properly formed DOCTYPE header - with nested exception:
[weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE heade
r]]]
at weblogic.webservice.util.WebServiceEarFile.init(WebServiceEarFile.java:183)
at weblogic.webservice.util.WebServiceEarFile.readDD(WebServiceEarFile.java:235)
at weblogic.webservice.util.WebServiceEarFile.<init>(WebServiceEarFile.java:74)
at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:177)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Please help as its urgent for me as we cannot have local installation of weblogic. We may just use the required jars.Weblogic version: 10.3
EJB Version: 2.x
Method for generating webservices fomr EJBs: servicegen task.
Application Build steps:
Step1) Maven to build the complete application and generate ejb-jar.jar and other projects jars and wars.
Step2) Post maven build success there is an ant script used to generate webservices using ejb’s in the project using servicegen task. Attached is build.xml for ant.
Following is the class path :
.;C:\PROGRA~1\IBM\SQLLIB\java\db2java.zip;C:\PROGRA~1\IBM\SQLLIB\java\db2jcc.jar;C:\PROGRA~1\IBM\SQLLIB\java\sqlj.zip;C:\PROGRA~1\IBM\SQLLIB\java\db2jcc_license_cu.jar;C:\PROGRA~1\IBM\SQLLIB\bin;C:\PROGRA~1\IBM\SQLLIB\java\common.jar;C:\Program Files\IBM\RationalSDLC\ClearQuest\cqjni.jar;C:\bea10.3\wlserver_10.3\server\lib\weblogic.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\webservices.jar;%JAVA_HOME%\lib\tools.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\libslf4j-log4j12-1.5.2.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\struts.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\bootstrap.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\db2jcc.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\db2jcc_license_cu.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\ehcache-core-2.0.0.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\j2ee.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\jdom.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\log4j-1.2.9.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\slf4j-api-1.5.8.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\ulc-dto.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\ulc-jar.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\scheduler-ejb.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\com.bea.core.xml.beaxmlbeans_2.0.0.0_2-5-1.jar;
Problem Area:
As you could notice in the yellow highlighted one that am referring to weblogic.jar from bea installation folder. Now if I use the weblogic.jar from the installation folder then build happens successfully.
However if I copy weblogic.jar to some other location say : C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\weblogic.jar
And include this path in the class path in place of weblogic.jar from the installation path, then I get the following errors: Please refer red highlighted part below…
C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\ulc-ear>ant
Buildfile: build.xml
ejbwebservice:
[servicegen] weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed D
OCTYPE header
[servicegen] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:301)
[servicegen] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:241)
[servicegen] at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:320)
[servicegen] at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:295)
[servicegen] at weblogic.ejb20.dd.xml.DDUtils.processEjbJarXML(DDUtils.java:265)
[servicegen] at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:118)
[servicegen] at weblogic.webservice.dd.EJBJarIntrospector.<init>(EJBJarIntrospector.java:47)
[servicegen] at weblogic.webservice.util.WebServiceEarFile.init(WebServiceEarFile.java:177)
[servicegen] at weblogic.webservice.util.WebServiceEarFile.readDD(WebServiceEarFile.java:235)
[servicegen] at weblogic.webservice.util.WebServiceEarFile.<init>(WebServiceEarFile.java:74)
[servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:177)
[servicegen] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[servicegen] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[servicegen] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[servicegen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[servicegen] at java.lang.reflect.Method.invoke(Method.java:597)
[servicegen] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[servicegen] at org.apache.tools.ant.Task.perform(Task.java:348)
[servicegen] at org.apache.tools.ant.Target.execute(Target.java:357)
[servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[servicegen] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[servicegen] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
[servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:758)
[servicegen] at org.apache.tools.ant.Main.startAnt(Main.java:217)
[servicegen] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[servicegen] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
[servicegen] --------------- nested within: ------------------
[servicegen] Error processing file 'META-INF/ejb-jar.xml'. weblogic.xml.process.XMLProcessingException: XML document doe
s not appear to contain a properly formed DOCTYPE header - with nested exception:
[servicegen] [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed
DOCTYPE header]
--------------- nested within: ------------------
weblogic.webservice.util.WebServiceJarException: Could not process ejb-jar C:\DOCUME~1\ac30416\LOCALS~1\Temp\ulc-ear.ear
-86826932\ejb.jar - with nested exception:
[weblogic.webservice.dd.EJBProcessingException: Can read in ejb DD files. - with nested exception:
[Error processing file 'META-INF/ejb-jar.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear
to contain a properly formed DOCTYPE header - with nested exception:
[weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE heade
r]]]
at weblogic.webservice.util.WebServiceEarFile.init(WebServiceEarFile.java:183)
at weblogic.webservice.util.WebServiceEarFile.readDD(WebServiceEarFile.java:235)
at weblogic.webservice.util.WebServiceEarFile.<init>(WebServiceEarFile.java:74)
at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:177)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Please help as its urgent for me as we cannot have local installation of weblogic. We may just use the required jars. -
Problems with client.jar - generated from webservices toolkit from JDK 1.1.7
We have deployed a web application using the webservices in WL 6.1 using JDK 1.3.1.
The clients were able to successfully access the servlet it generated and download
the client.jar. Unfortunately this client.jar seems to be dependent on JDK 1.2
and beyond. It seems to use java.util.Map class in the JNDI-SOAP SPI.
Is there any workaround or fix to this problem, so this jar can be used from a
JDK 1.1.7 env?.
Our objective is to use WL 6.1 EJB's from WL 4.5.1 using Webservices. Are there
any known problems with this approach (Ofcourse other than this).
Thank you.
Dora Potluri
Here is the stack trace from using the client.jar
Class not found java.lang.ClassNotFoundException: java.util.Map
[Root exception is java.lang.ClassNotFoundException: java.util.Map]javax.naming.
NamingException: Class not found java.lang.ClassNotFoundException: java.util.Map
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at javax.naming.NamingException.<init>(Compiled Code)
at weblogic.soap.http.SoapContext.throwNamingException(Compiled Code)
at weblogic.soap.http.SoapContext.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(Compiled Code)
at weatherEJB.WeatherBean.getTemp(Compiled Code)
at weatherEJB.WeatherBeanEOImpl.getTemp(Compiled Code)
at weatherEJB.WeatherBeanEOImpl_WLSkel.invoke(Compiled Code)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(Compiled Code
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(Compiled
Co
de)
at weblogic.rmi.extensions.BasicRequestDispatcher$BasicExecuteRequest.ex
ecute(Compiled Code)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code)
Fri Sep 21 10:47:12 CDT 2001:<I> <EJB> Transaction: '1001087185816_1' rolled bac
k due to EJB exception:Yes, there is an expectation that the client jar will be run on JDK 1.3x. WLS 6.1 is certified on JDK 1.3x only. This
applies to the WebServices client as well. For details on platform support see
http://e-docs.bea.com/wls/platforms/index.html
Thanks,
Jim
Jim Rivera
Product Manager, WebLogic Server
BEA Systems, Inc.
Dora Potluri wrote:
I started testing using the client.jar generated by webservices WL 6.1 and found
that it uses reflection API interfaces that are not available til JDK 1.3. Is
there an expectation that the clients of Webservices are all going to be JDK 1.3.X.
Here is the stack trace we get.
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.soap.http.SoapContext.lookup(SoapContext.java:76)
at javax.naming.InitialContext.lookup(InitialContext.java:280)
at weatherEJB.WeatherBean.getTemp(WeatherBean.java:106)
at weatherEJB.WeatherBeanEOImpl.getTemp(WeatherBeanEOImpl.java:47)
at weatherEJB.WeatherBeanEOImpl_WLSkel.invoke(WeatherBeanEOImpl_WLSkel.java:90)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:261)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:56)
at weblogic.rmi.extensions.BasicRequestDispatcher$BasicExecuteRequest.execute(BasicRequestDispatcher.java:166)
at weblogic.t3.srvr.ExecuteThread.run(Compiled Code) -
HOT deployment problem with WebLogic 5.1sp11
Hello!
We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJB DeployerTool.
When we registered our jar in the weblogic.properties file - everything is OK.
This ejb cotains correct EJB's which are made in EJB 1.1 standard.
In the WebLogic EJB DeployerTool I attach proper WeaWeblogic application server
(it works on another computer, but tool found our server confidently. Then I opened
my jar file. Tool parsed file and found all beans.
After all I'm trying to run Tools/Deploy and I have the error message showed below.
If somebody knows how to manage with this problem, help!
weblogic.ejb.common.DeploymentException: Problem creating deployment ftp://172.16.2.108:21C:/tmp2/StaffShell.jar
from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
java.lang.NullPointerException:
Start server side stack trace:
java.lang.NullPointerException
at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
at java.net.URL.openStream(URL.java:798)
at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
End server side stack trace
java.lang.NullPointerException:
Start server side stack trace:
java.lang.NullPointerException
at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
at java.net.URL.openStream(URL.java:798)
at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
End server side stack trace
Deployment failed.Is SP11 jars in the client classpath or not, before launching DeployerTool.
If yes, then it looks like a bug. You might want to report this problem to
[email protected]
Kumar
"Anton Nazarov" <[email protected]> wrote in message
news:[email protected]...
>
Hello!
We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJBDeployerTool.
When we registered our jar in the weblogic.properties file - everything isOK.
This ejb cotains correct EJB's which are made in EJB 1.1 standard.
In the WebLogic EJB DeployerTool I attach proper WeaWeblogic applicationserver
(it works on another computer, but tool found our server confidently. ThenI opened
my jar file. Tool parsed file and found all beans.
After all I'm trying to run Tools/Deploy and I have the error messageshowed below.
>
If somebody knows how to manage with this problem, help!
weblogic.ejb.common.DeploymentException: Problem creating deploymentftp://172.16.2.108:21C:/tmp2/StaffShell.jar
from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
java.lang.NullPointerException:
Start server side stack trace:
java.lang.NullPointerException
at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
va:108)
>
at java.net.URL.openStream(URL.java:798)
atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
va:322)
>
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
>
atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
>
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
>
atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java:347)
>
atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:96)
>
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
>
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
End server side stack trace
java.lang.NullPointerException:
Start server side stack trace:
java.lang.NullPointerException
at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
va:108)
>
at java.net.URL.openStream(URL.java:798)
atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
va:322)
>
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
>
atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
>
at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
>
atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java:347)
>
atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:96)
>
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
>
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
End server side stack trace
Deployment failed. -
Issue with weblogic.jar parsing the wsdl
Hi,
Here is a very small program, for which i am facing the problem of getting the
types from the wsdl. It works fine, as standalone....You do not have to deploy
the code any where..just have weblogic.jar in the classpath. It does not work.
It works when weblogic.jar is not in the classpath..any help is GREATLY APPRECIATED...
java.wsdl.Types from the java.wsdl.Definition object and the schema in the types
is null ( when weblogic.jar is present in the
I am always getting null in the schema (
import javax.wsdl.Definition;
//import weblogic.soap.wsdl.binding.Definition;
import javax.wsdl.xml.WSDLReader;
import javax.wsdl.factory.WSDLFactory;
public class Test {
Definition definition = null;
public static void main(String args[] ) {
Test test = new Test();
test.parseWSDL(args[0]);
public void parseWSDL(String WSDLName)
try
WSDLFactory wsdlFactory = WSDLFactory.newInstance();
WSDLReader wsdlReader = wsdlFactory.newWSDLReader();
wsdlReader.setFeature("javax.wsdl.verbose",false);
wsdlReader.setFeature("javax.wsdl.importDocuments",true);
definition = wsdlReader.readWSDL(WSDLName);
System.out.println("-----------" + definition.getTypes() );
catch( Exception e ) {
System.out.println("Exception" + e ); }
Thank for your help.
NagHi Nag,
With little reference to Sir Walter Scott, it would be a very tangled
web we weave in an attempt to factor out the inter-relationships of
javax interfaces that are hindering your effort. All to say, we don't
currently support JSR 110 (javax.wsdl.*) and it is not on the near term
horizon.
Have you considered using autotype [1]?
Regards,
Bruce
[1]
http://edocs.bea.com/wls/docs81/webserv/anttasks.html#1080062
Nag wrote:
>
Hi,
Here is a very small program, for which i am facing the problem of getting the
types from the wsdl. It works fine, as standalone....You do not have to deploy
the code any where..just have weblogic.jar in the classpath. It does not work.
It works when weblogic.jar is not in the classpath..any help is GREATLY APPRECIATED...
java.wsdl.Types from the java.wsdl.Definition object and the schema in the types
is null ( when weblogic.jar is present in the
I am always getting null in the schema (
import javax.wsdl.Definition;
//import weblogic.soap.wsdl.binding.Definition;
import javax.wsdl.xml.WSDLReader;
import javax.wsdl.factory.WSDLFactory;
public class Test {
Definition definition = null;
public static void main(String args[] ) {
Test test = new Test();
test.parseWSDL(args[0]);
public void parseWSDL(String WSDLName)
try
WSDLFactory wsdlFactory = WSDLFactory.newInstance();
WSDLReader wsdlReader = wsdlFactory.newWSDLReader();
wsdlReader.setFeature("javax.wsdl.verbose",false);
wsdlReader.setFeature("javax.wsdl.importDocuments",true);
definition = wsdlReader.readWSDL(WSDLName);
System.out.println("-----------" + definition.getTypes() );
catch( Exception e ) {
System.out.println("Exception" + e ); }
Thank for your help.
Nag -
Encoding with weblogic.jar or wlclient.jar
I am using weblogic 9.0 on jrockit 1.5.0_03 I have an application deployed using stateless session EJB’s.
I have a webstart client that runs on jdk1.5.0_03. When using weblogic.jar on the client side, everything runs fine.
When using wlclient.jar on the client side, I don’t get data from the server which contains umlauts. The data are lost on the client side.
In the direction to the server I have no problems, I can store data with umlaut. I tried already setting the default encoding on server (-Dweblogic.webservice.i18n.charset=utf-16) and client (-Dfile.encoding=utf-16), with no success.
Any help will be appreciated.
Thanks in advance!Hello Sir
Did u solve the problem
i am also getting the same problem
please help me if u found the solution -
Problem with weblogic.deploy and cluster
I'm having some problems with the weblogic.deploy class when trying to refresh
a jsp file. Using the following command to redeploy the entire application works
fine:
java weblogic.deploy -port 9876 -host apptest01 update
administrator portal c:\portal-site
However using the following command to refresh just one jsp
file:
java weblogic.deploy -url t3://apptest01:9876 -username system
-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
refresh administrator portal
produces the following stack trace:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.management.home.olbcluster.
Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
remaining name ''
at weblogic.rmi.internal.BasicOutboundRequest.
sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
invoke(ReplicaAwareRemoteRef.java:255)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
invoke(ReplicaAwareRemoteRef.java:222)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy0.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.
lookup(WLContextImpl.java:323)
at weblogic.management.tools.WebAppComponentRefreshTool.
getMBeanHomeForManagedServer
WebAppComponentRefreshTool.java:498)
at weblogic.management.tools.
WebAppComponentRefreshTool.
getComponentMBeanForServer
(WebAppComponentRefreshTool.java:225)
at weblogic.management.tools.
WebAppComponentRefreshTool.findInternalPaths
(WebAppComponentRefreshTool.java:187)
at weblogic.management.tools.WebAppComponentRefreshTool.
refresh(WebAppComponentRefreshTool.java:151)
at weblogic.deploy.refresh(deploy.java:704)
at weblogic.deploy.runBody(deploy.java:374)
at weblogic.utils.compiler.Tool.run(Tool.java:79)
at weblogic.deploy.main(deploy.java:1601)
Unable to resolve weblogic.management.home.olbcluster.
Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
Any ideas?
"John Murphy" <[email protected]> wrote:
>
>I'm having some problems with the weblogic.deploy class when trying to
>refresh
>a jsp file. Using the following command to redeploy the entire application
>works
>fine:
>
>java weblogic.deploy -port 9876 -host apptest01 update
>administrator portal c:\portal-site
>
>However using the following command to refresh just one jsp
>file:
>
>java weblogic.deploy -url t3://apptest01:9876 -username system
>-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
>refresh administrator portal
>
>produces the following stack trace:
>
>javax.naming.NameNotFoundException: Unable to resolve
>weblogic.management.home.olbcluster.
>Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
>remaining name ''
> at weblogic.rmi.internal.BasicOutboundRequest.
> sendReceive(BasicOutboundRequest.java:85)
> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
> invoke(ReplicaAwareRemoteRef.java:255)
> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
> invoke(ReplicaAwareRemoteRef.java:222)
> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
> at $Proxy0.lookup(Unknown Source)
> at weblogic.jndi.internal.WLContextImpl.
> lookup(WLContextImpl.java:323)
> at weblogic.management.tools.WebAppComponentRefreshTool.
> getMBeanHomeForManagedServer
> WebAppComponentRefreshTool.java:498)
> at weblogic.management.tools.
> WebAppComponentRefreshTool.
> getComponentMBeanForServer
> (WebAppComponentRefreshTool.java:225)
> at weblogic.management.tools.
> WebAppComponentRefreshTool.findInternalPaths
> (WebAppComponentRefreshTool.java:187)
> at weblogic.management.tools.WebAppComponentRefreshTool.
> refresh(WebAppComponentRefreshTool.java:151)
> at weblogic.deploy.refresh(deploy.java:704)
> at weblogic.deploy.runBody(deploy.java:374)
> at weblogic.utils.compiler.Tool.run(Tool.java:79)
> at weblogic.deploy.main(deploy.java:1601)
>Unable to resolve weblogic.management.home.olbcluster.
>Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
>
>Any ideas?
>
Hi John,
How's tricks?
It looks to me as though the olbcluster JNDI reference isn't being resolved from
the tree. A similar error results when a Connection Pool cannot be resolved, the
JNDI context env.jdbc is resolved but the particlar pool isn't. In my experience
it often turns out to be an error in the correlation between the deployment descriptors,
settings applied via the console and references made in the code.
That's my tuppence worth,
James :-)
-
Problems with weblogic clustering setup
Hi all, I'm having problems extending a weblogic 9.2 cluster from vertical to orizontal. The environment is composed by two physical servers A and B. On A it's running the node manager, the admin console and two nodes, on B I've just installed weblogic 9.2, registered the licence.
I'm reading this guide: http://egeneration.beasys.com/wls/docs103/cluster/setup.html#wp742559 but I think this guide is non clear.
1) I added the new machine into the admin console
2) I added the new server to the configuration (environmnent -> cluster)
3) I created a new node on the new server and I associate it to the cluster and machine.
moreover I checked the ports so that it should be set correctly.
After I start the nodemanager into B and after adminconsole from A tries to connect to B I get this into the console
[root@engtest4 bea]# /opt/bea/weblogic92/server/bin/startNodeManager.sh
+ CLASSPATH=/opt/bea/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit90_150_10/lib/tools.jar:/opt/bea/weblogic92/server/lib/weblogic_sp.jar:/opt/bea/weblogic92/server/lib/weblogic.jar:/opt/bea/weblogic92/server/lib/webservices.jar:/opt/bea/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit90_150_10/lib/tools.jar:/opt/bea/weblogic92/server/lib/weblogic_sp.jar:/opt/bea/weblogic92/server/lib/weblogic.jar:/opt/bea/weblogic92/server/lib/webservices.jar::/opt/bea
+ export CLASSPATH
+ export PATH
+ cd /opt/bea/weblogic92/common/nodemanager
+ set -x
+ '[' '' '!=' '' ']'
+ '[' '' '!=' '' ']'
+ /opt/bea/jrockit90_150_10/bin/java -jrockit -Xms128m -Xmx256m -Xverify:none -Djava.security.policy=/opt/bea/weblogic92/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/opt/bea/jrockit90_150_10 weblogic.NodeManager -v
<Jan 14, 2009 5:10:22 PM> <INFO> <Loading domains file: /opt/bea/weblogic92/common/nodemanager/nodemanager.domains>
<Jan 14, 2009 5:10:23 PM> <INFO> <Loading identity key store: FileName=/opt/bea/weblogic92/server/lib/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Jan 14, 2009 5:10:23 PM> <INFO> <Loaded node manager configuration properties from '/opt/bea/weblogic92/common/nodemanager/nodemanager.properties'>
Node manager v9.2.2.0
Configuration settings:
NodeManagerHome=/opt/bea/weblogic92/common/nodemanager
ListenAddress=
ListenPort=5556
ListenBacklog=50
SecureListener=true
AuthenticationEnabled=true
NativeVersionEnabled=true
CrashRecoveryEnabled=false
JavaHome=/opt/bea/jrockit90_150_10/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/opt/bea/weblogic92/common/nodemanager/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1
LogAppend=true
LogToStderr=true
LogFormatter=weblogic.nodemanager.server.LogFormatter
DomainsFile=/opt/bea/weblogic92/common/nodemanager/nodemanager.domains
DomainsFileEnabled=true
StateCheckInterval=500
Domain name mappings:
wl_server -> /opt/bea/weblogic92/samples/domains/wl_server
base_domain -> /opt/bea/user_projects/domains/base_domain
<Jan 14, 2009 5:10:24 PM> <INFO> <Secure socket listener started on port 5556>
<Jan 14, 2009 5:10:38 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:595)
<Jan 14, 2009 5:11:54 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:595)
<Jan 14, 2009 5:11:54 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:595)
should server A and B have the same domain configuration? (same files)
Regards
MarcoYes, you must have the same domain configuration on the server B. Usually I copy the domain directory on the server B to have the same configuration. the directory with "salt file" should be the "<domain_dir>/security"...
Hope this helps...
Mariano -
Problem with weblogic deployment descriptor tool (DDInit)
Hi,
I'm just playing with weblogic ... following their tutorual but I can't seem to run their deployment descriptor tool:
java weblogic.ant.taskdefs.war.DDinit <folderName> gives me a NoClassDefFoundError.
I have weblogic6.0sp1 installed with an evaluation license which has not yet expired. I have d:\bea\wlserver6.0sp1\lib in mt classpath so weblogic.jar is n there.
When I check out the contents of the weblogic.jar file .. I can't seem to find this tool.
Can anyone give me a clue as to what I am doing wrong?Here's a link describing the process. If this is what you are doing then your problem may be that 6.0 doesn't support this.
http://edocs.bea.com/wls/docs61/programming/packaging.html#pack004
Maybe you are looking for
-
Connecting FIreWire to MACBook PRO
I have a SmartDisk FireLite drive i used on my old MAC for back-ups. It only has a FireWire port. My new MACBook Pro only has USB ports. How do I connect them?
-
Script logic : determine the content of a variable according to a IF test
Hello experts, I have the following need in a script logic determine the content of a variable according to a IF test For example I tried : *WHEN %ENTITY% *IS "CH20","CH30","ES10" *SELECT(%ENTITYPBPD%, "[ID]", "ENTITYCC", "[ID] = '%ENTITYCC_SET%_PBPD
-
PLS-00114: identifier too long error (Oracle 10g)
Hi All, Hi All, I have created procedure called "p_procedure_for_cals_annual_sal_oracle_proprierty.lib". It is must to give the procedure name as mentioned.(>30 Chars) But while executing I am getting following error. SQL> exec p_procedure_for_cals_a
-
Imac superdrive don't eject the DVD
I tried in all way, openfirmware included but the DVD is always inside my Imac. Is there another way to put out it??? Please is very urgently Thanks Romolo
-
Package jawa.awt does not exist
I have searched this problem in the forum but could not find anything about it. I have NetBeans IDE + JDK 5.0 Update 3 installed in my computer (http://java.sun.com/j2se/1.5.0/download.jsp). But when I try to compile a very simple Java using any pack