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.
Similar Messages
-
Hot deployment problems with weblogic 7.0 sp2
Hi Guys
I am trying out hot deplyment of a j2ee application on WebLogic Server 7.0 SP2
Approach 1
The application is deployed in exploded ear format from the folder
d:/work/testbed/ear. The appropriate entry in config.xml looks like this.
<Application Deployed="true" Name="Testbed"
Path="D:\tools\bea702\projects\testbed\applications\testbed"
StagedTargets="" TwoPhase="false">
<EJBComponent Name="SessionBeans" Targets="myserver" URI="SessionBeans.jar"/>
</Application>
Creating or touching the REDEPLOY file in META-INF folder doesnt cause hot
deployment to occur
Approach 2
Copied the ear file to the applications folder. Creating or touching the
REDEPLOY file in META-INF file caused the application to be redeployed.
However the weblogic console is constantly spitting out this message.
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:51 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:52 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
It seems that the application is getting undeployed and reactivated every 5
seconds.
Questions
1) Any reasons why approach 1 didnt work
2) What could be causing this constant undeployment and reactivation
Thanks for your time
anandI think I figured out what is causing the application to be redployed every 5
seconds. It seems that if the application is deployed in the weblogic domains
applications folder you should NOT create a <Application element. Weblogic
automatically recognizes all applications in this folder and deploys them.
Removing the application entry (as shown in Approach 1) from the config.xml
and hot deploying by touching the REDEPLOY file did the trick.
One question still remains. Is hot deployment only possible when I copy the
exploded ear to the domain "applications" folder
Thanks for your time
anand
ps : The idea of trying it without the <Application element came from trying
out hot deployment in Weblogic 8. WLS8 first deploys the application in the
applications folder, followed by the application configured in the
<Application element. Since both the applications were essentially the same it
gave me a JNDIException saying that some entity is already bound with the same
name. Weblogic 7 however doesnt complain at this point.
- anand
In article <[email protected]>, Anand Raman wrote:
Hi Guys
I am trying out hot deplyment of a j2ee application on WebLogic Server 7.0 SP2
Approach 1
The application is deployed in exploded ear format from the folder
d:/work/testbed/ear. The appropriate entry in config.xml looks like this.
<Application Deployed="true" Name="Testbed"
Path="D:\tools\bea702\projects\testbed\applications\testbed"
StagedTargets="" TwoPhase="false">
<EJBComponent Name="SessionBeans" Targets="myserver" URI="SessionBeans.jar"/>
</Application>
Creating or touching the REDEPLOY file in META-INF folder doesnt cause hot
deployment to occur
Approach 2
Copied the ear file to the applications folder. Creating or touching the
REDEPLOY file in META-INF file caused the application to be redeployed.
However the weblogic console is constantly spitting out this message.
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:51 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:52 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
Undeploying EJB Component SessionBeans
<Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
<Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
It seems that the application is getting undeployed and reactivated every 5
seconds.
Questions
1) Any reasons why approach 1 didnt work
2) What could be causing this constant undeployment and reactivation
Thanks for your time
anand -
Web Module Deployment Problem with Weblogic [Deployer:149026]
Dear Friends,
I've been facing a problem during deploying an Web Module on Weblogic 8.1. The name of my webmodule is 'MyOraWebModule'.
When I first developed, deployed and tested it in Weblogic 8.1, it was deployed and worked fine. But on the next day, when I tried to redeploy it, the deployment failed. This thing not just happens only once.. it is happeing always i.e. if I develop a new webmodule and deploy/redeploy it, it will work fine ONLY ON THE FIRST DAY (i.e. the day when the web module is created), but on the next day, it shows the following error if I try to redeploy it. The error is:
Task 3 failed: [Deployer:149026]Deploy application MyOraWebModule on myserver.
Deployment failed on Server myserver
Exception:weblogic.management.ApplicationException: prepare failed for MyOraWebModule
Module: MyOraWebModule Error: Context path 'MyOraWebModule' is already in use by the module: MyOraWebModule
Any suggestion or, guideline from you will be highly appreciated.
With Thanks,
... ChistyNot sure if you are still looking for the answer. I have a similar problem, I have a work around on it but still trying to identify what the issue is. I have deployed multiple web application modules on weblogic 8.1 and on the redeploy I was gettig the exception weblogic.management.ApplicationException: prepare failed for USER_DEFINED_MODULE_NAME
Context path '/' is already in use by the module. when this exception is thrown I observed that the targets attribute of tag WebAppComponent is initialized to the server name. If I stop the server, make the value of the targets attribute to be empty string in config.xml and start the server, the server starts fine. And I could continue. Not sure why this is so since the targets attribute is used to identify on what servers the application needs to be deployed.
Any input on why the weblogic 8.1 is behaving this way when the targets attribute is defined with a value would of great help.
thanks, -
EAR Deployment Problem with weblogic 10.2. Need help.
Hi,
I have a EAR file exported from MyEclipse IDE. When i am deploying the EAR file in weblogic 10.2, i am not seeing classess and properties were not exploded under WEB-INF/classes in the web project. I can see the classes folder but it's empty.
When i opened i can see EJB project JAR file and web project .war file in the EAR file. I checked the .war file content and i can see all the classes and properties available in the .war file.
Please help me to find, why the classes and properties are not being exploded when i am deploying as package.
Note: When i am deploying from myeclipse as exploded deployment i was able to run the application but i am failing when i deploy as a package (.ear file).
Thank you,
Vijay MI found the answer to this. The documentation is not clear enough, LD_LIBRARY_PATH MUST be set and MUST have a pointer to the directory where the SSL .so modules are. I wrote up a blog article explaining the configuration and detailed this issue.
http://blogs.oracle.com/irm/2010/06/quick_guide_to_oracle_irm_11g_1.html -
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 -
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? -
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
-
Exploded (hot) deployment on a Weblogic cluster
AFAIK, exploded hot deployment on a Weblogic cluster is not supported through OEPE.
When deploying an application on a cluster, each change, no matter how small, forces you to republish these changes, ultimately causing the application to be redeployed by OEPE. Turnaround time for this (depending on the app) can take some time.
Is there a workaround available for this ?
I'm looking for a way to minimize the turnaround time between developing code, and actual seeing the code changes on the screen. The requirement however is that deployments should be possible on a managed instance / cluster (non AdminServer).
Does Oracle Weblogic support such "hot deployment" capabilities from an IDE like Eclipse ? Does anybody here have such a process in place ? (perhaps using ant / maven2 tooling)Hi
I want to clarify that the application has to be deployed to a cluster of two managed servers, amandad_Server_1 (On Windows server hosting console) and amandad_Server_2 which is running in other Windows server.
I deployed the application following your recdommendations and the resulta is as follows:
Windows server (running the console)
1 EAR file was copied to ... \user_projects\domains\amanda_domain\servers\amandad_Server_1\stage
2. The application files extractected from the EAR files were copied to \user_projects\domains\amanda_domain\servers\amandad_Server_1\tmp
Windows Server not runn ing the console
No files were copied to neither
... \user_projects\domains\amanda_domain\servers\amandad_Server_2\stage
\user_projects\domains\amanda_domain\servers\amandad_Server_2\tmp
Questions
1 Windows server not running the console the files were not copied....What might cause this behaviour....? how to fixi it...?
2. Do I have to manaully copy the files to folders
...\user_projects\domains\amanda_domain\servers\amandad_Server_2\stage
... \user_projects\domains\amanda_domain\servers\amandad_Server_2\tmp -
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 :-)
-
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 -
Problem with weblogic server help me...!
HI,
i have developed and application that was deployed successfully in Tomcat 5.0, but it was not with weblogic 8...
plz help me... thanks in advance..In this case, I would call the OP up from asking a stupid question, with no details at all, rather than Soultech for responding to it in humorous manner.
Hence why I included that link to "How to ask smart questions"
"It doesn't work on Weblogic" will not get any helpful responses
WHAT doesn't work?
Is there an error message?
What have you tried?
The onus is on the OP to post a clear and concise description of his problem, along with error messages/stack traces, anything else that may help diagnose the issue.
I believe Soultechs post was justified, if a little short. -
Problem with Weblogic 8.1 Sp2 and Struts 1.1 + tiles
I am using weblogic 8.1 sp2 with struts and tiles.
I am getting the follwing error in my web pages, which is not consistent.
The error stack trace is as below.
[java] <Oct 6, 2005 12:23:53 PM GMT+05:30> <Error> <HTTP> <BEA-101309> <[ServletContext(id=3212
195,name=awmweb,context-path=/awm)] could not deserialize the context attribute "org.apache.struts.
iles.DEFINITIONS_FACTORY"
[java] java.io.NotSerializableException: com.awm.awm.controllers.layout.BaseLayoutControll
r
[java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
[java] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
[java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
[java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
[java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
[java] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
[java] at java.util.HashMap.writeObject(HashMap.java:978)
[java] at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
25)
[java] at java.lang.reflect.Method.invoke(Method.java:324)
[java] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
[java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
[java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
[java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
[java] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
[java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
[java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
[java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
[java] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
[java] at java.util.HashMap.writeObject(HashMap.java:978)
[java] at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
25)
[java] at java.lang.reflect.Method.invoke(Method.java:324)
[java] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
[java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
[java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
[java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
[java] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
[java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
[java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
[java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
[java] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
[java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
[java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
[java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
[java] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
[java] at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.
ava:136)
[java] at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
[java] at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
[java] at weblogic.servlet.internal.WebAppServletContext.getAttribute(WebAppServletContext.
ava:619)
[java] at org.apache.struts.tiles.TilesUtilStrutsModulesImpl.getDefinitionsFactory(TilesUti
StrutsModulesImpl.java:145)
[java] at org.apache.struts.tiles.TilesUtilStrutsModulesImpl.getDefinitionsFactory(TilesUti
StrutsModulesImpl.java:133)
[java] at org.apache.struts.tiles.TilesUtil.getDefinitionsFactory(TilesUtil.java:186)
[java] at org.apache.struts.tiles.TilesUtil.getDefinition(TilesUtil.java:224)
[java] at org.apache.struts.taglib.tiles.util.TagUtils.getComponentDefinition(TagUtils.java
339)
[java] at org.apache.struts.taglib.tiles.DefinitionTag.doStartTag(DefinitionTag.java:261)
[java] at com.awm.awm.jsp._errors.__500_45_servererror._jspService(__500_45_servererro
.java:208)
[java] at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
[java] at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStub
mpl.java:971)
[java] at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
[java] at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
[java] at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
[java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
[java] at com.awm.awm.filters.AWMBaseFilter.doFilter(AWMBaseFilter.java:97)
[java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
[java] at com.awm.awm.quote.QuoteUsageFilter.doFilter(QuoteUsageFilter.java:70)
[java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
[java] at com.awm.awm.filters.AWMBaseFilter.doFilter(AWMBaseFilter.java:97)
[java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
[java] at com.awm.awm.filters.FrontFilter.doFilter(FrontFilter.java:160)
[java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
[java] at com.awm.awm.filters.JTidyFilter.doFilter(JTidyFilter.java:152)
[java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
[java] at com.awm.awm.filters.PerfLogFilter.doFilter(PerfLogFilter.java:211)
[java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
[java] at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.jav
:305)
[java] at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:
23)
[java] at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletConte
t.java:3908)
[java] at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext
java:3683)
[java] at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585
[java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
[java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
[java] >
Can any one comment on why I am getting this error? Is it related to the hot deployment issue? Please comment.
Thanks in advance,
KHi,
Generally this type of exception raised by a class or the serialization runtime when a class may not be serialized.The argument should be the name of the class.
You might be forgot to implement the serializable interface for the class in struts frame work.
check it properly.
Regards
Anilkumar kari -
Deployment Problem in weblogic
Hi,
This is Niranjan Reddy. I am using JDeveloper 10.1.3 with weblogic 9i. When I deploy the application in to a weblogic server from a Jdeveloper I am getting the following error.
Can any one can solve my problem.
F:\full version of Jdeveloper\full version of Jdeveloper\jdevstudio1013\jdk\jre\bin\javaw.exe -classpath C:\beahome\weblogic90\server\lib\weblogic.jar weblogic.Deployer -adminurl http://localhost:7001 -user niranjan -password **** -debug -verbose -deploy -upload -source F:\full version of Jdeveloper\full version of Jdeveloper\jdevstudio1013\jdev\practice\firstdeploy\firstsample\deploy\firstdeploy.ear -name firstdeploy
weblogic.Deployer invoked with options: -adminurl http://localhost:7001 -user niranjan -debug -verbose -deploy -upload -source F:\full version of Jdeveloper\full version of Jdeveloper\jdevstudio1013\jdev\practice\firstdeploy\firstsample\deploy\firstdeploy.ear -name firstdeploy
[WebLogicDeploymentManagerImpl.<init>():102] : Constructing DeploymentManager for J2EE version V1_4 deployments
[WebLogicDeploymentManagerImpl.getNewConnection():145] : Connecting to admin server at localhost:7001, as user niranjan
[ServerConnectionImpl.getEnvironment():252] : setting environment
[ServerConnectionImpl.getEnvironment():255] : getting context using http://localhost:7001
[ServerConnectionImpl.close():298] : Closing DM connection
[ServerConnectionImpl.close():318] : Unregistered all listeners
weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://localhost:7001': Destination unreachable; nested exception is:
java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:306)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:143)
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:93)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.Deployer.run(Deployer.java:70)
at weblogic.Deployer.main(Deployer.java:54)
Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:120)
at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:398)
at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:287)
... 6 more
Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:131)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:147)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:117)
... 9 more
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: http://localhost:7001: Destination unreachable; nested exception is:
java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:48)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:739)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:343)
at weblogic.jndi.Environment.getContext(Environment.java:257)
at weblogic.jndi.Environment.getInitialContext(Environment.java:165)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:294)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:266)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:129)
... 11 more
Caused by: java.net.ConnectException: http://localhost:7001: Destination unreachable; nested exception is:
java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:137)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:324)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:319)
... 16 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'localhost' and port: '7001' a WebLogic Server?; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:465)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:255)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:199)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:220)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:187)
... 21 more
Thanks in advance
NIRANJAN REDDYJDeveloper 10.1.3.3 configures a connection with WebLogic server with the t3 protocol.The deployment profile has the connection protocol specified as http. Modify the connection protocol in the deployment profile.
1. In the Deployment Profile Properties window select the Platform>WebLogic 9.x node.
2. In the WebLogic 9.x Deploy command modify:
-adminurl http://${hostname}:${port} to
-adminurl t3://${hostname}:${port} -
How to hot deploy EJB in Weblogic?
Hi all,
We use Weblogic 10.3 and EJB3.
EJB has been build as ear and deployed in the server. And other deployed modules in server calls that.
But the modification of EJB need to be rebuilt and restart the server.
Does Weblogic support hot deploy for EJB? Do we need plugin or something else for this feature?
Thanks a lot.Hi,
The production redeployment strategy/hot deployment is supported for:
a. Standalone Web Application (WAR) modules and Enterprise applications (EARs) whose clients access the application via a Web application (HTTP).
b. Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.
c. All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.
Production redeployment is not supported for:
a. Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.
b. Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC for Oracle WebLogic Server.
c. Applications that obtain JDBC data sources via the DriverManager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.
d. Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.
Please check the below Doc
http://docs.oracle.com/cd/E14571_01/web.1111/e13702/redeploy.htm#
Hope this answers your question!!
Thanks,
Vijaya -
I've got an exception
<07.11.2004 18:20:22 MSK> <Error> <HTTP> <BEA-101216> <Servlet: "Faces Servlet"
failed to preload on startup in Web application: "MyApp".
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubIm
pl.java:906)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStub
Impl.java:842)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
mpl.java:782)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
ervletContext.java:3236)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebApp
ServletContext.java:3193)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebApp
ServletContext.java:3179)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAp
pServletContext.java:3154)
at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java
:654)
at weblogic.servlet.internal.WebService.preloadResources(WebService.java
:483)
at weblogic.servlet.internal.ServletInitService.resume(ServletInitServic
e.java:30)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
at weblogic.Server.main(Server.java:32)
>
JSF v.1.1
Does JSF work with WebLogic?Have you already figured it out? I have the same
problem to deploy a jsf war file to Weblogic 8.1.I got it working on wls 8.1 sp2. This is a work around for some of us who need to work with existing products and any upgrade to a newer version takes its own sweet time. Read below ...
1. Work-around for �listener� in web.xml not working
a. Create InitFacesContext Servlet
public class InitFacesContext extends GenericServlet {
StartupServletContextListener listener;
public void destroy() {
super.destroy();
listener.contextDestroyed(new ServletContextEvent(getServletContext()));
public void init(ServletConfig arg0) throws ServletException {
super.init(arg0);
listener = new StartupServletContextListener();
listener.contextInitialized(new ServletContextEvent(getServletContext()));
public void service(ServletRequest arg0, ServletResponse arg1) throws ServletException, IOException {
}b. Configure web.xml
<!--
<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
</listener>
-->
<servlet>
<servlet-name>InitFacesContext</servlet-name>
<servlet-class>com.gene.volts.servlet.InitFacesContext</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet>
<servlet-name>FacesServlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>2. JSP 2.0 requirement
a. Download jsp-api.jar (like from Tomcat 5.x distribution ;-) ) and include it in web-inf/lib
3. Dealing with FacesContext not being initialized error
a. web.xml configuration
<servlet-mapping>
<servlet-name>FacesServlet</servlet-name>
<url-pattern>*.faces</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>b. Redirect
<jsp:forward page="/abc.faces"/>
Maybe you are looking for
-
Can't read books on KOBE, ADE crashes when I try to open book
ADE 4.02 iMac 10.10.1 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 I reloaded ADE & deleted the book and borrowed it
-
ATI catalyst 11.3-1 + Xserver 1.9.4
First off, i dont think i am a noob, but still pretty unexpired so sorry if stuff don't make sense, or if i post in the fail forumsection. I have just reinstalled Arch because my root directory was about to blow over. So i did. Unfortonatly the newes
-
Macbook keeps losing wireless link to HP printer
My Macbook links to HP printer wirelessly fine when its just started up but after time of not using printer Macbook loses wireless connection. In HP Utility software it gives error message ' looking for printer' or devicde not found. I've followed HP
-
HT1338 Burn iPhone movies to DVD
I have an iPhone 4S and a MacBook Pro. Does anyone know how to burn iPhone movies to a DVD so it can play on my DVD player? Thx.
-
External drives and disk space for iPhoto, iTunes...
I'm ill and cannot spend much time sitting at a desk, so I have to a MacBook (aka, when real sick, I can work in a layZboy or in bed). So now I have the 17" MBP with 500G, and should upgrade the GHz to 8 as soon as prices drop. Here WAS my plan: I'd