JNDI Exception on re-deployment to a cluster
I'm getting an error that I have not seen in the newsgroups so far. It
happens when I deploy what I believe to be a properly configured clusterable
application (.ear file) to my cluster.
Here's my setup:
WebLogic 6.0 sp1, three instances across 2 machines. The admin server (wl1)
is running on Stimpy (win2kAS) on 10.10.10.21 (it is not part of the
cluster). The 1st managed server (app1) is also on Stimpy bound to
10.10.10.22 (a virtual IP). The second managed server (app3) is on Ren
(also win2kAS) at 10.10.10.23. Auto-deploy is off. I am using the console
to deploy the app. (I turned auto-deploy off because the app was getting
deployed to the admin server automatically and throwing an error because of
the clustered HTTP session state)
Here's what happens.
I start up all of the instances with no apps deployed. Everything appears
to be running fine. No errors. I then use the console to deploy my
application (sample1.0.ear). I select only the cluster as the target for
the EJB and the webapp. If I try to access the app at this point I just get
404's. I then restart all of the servers and the app gets deployed across
the cluster with no errors. I can access everything JSPs, servlets, and an
EJB without issue.
My problem comes when I try to re-deploy the application. I have tried this
using the console, and by copying the new .ear file to the applications
directory on the admin server. I always get the same error, and it only
shows up on "app1" the first managed server in the cluster. Below is the
output form the log:
Undeploying EJB Component HelloWorldEJB
<Apr 16, 2001 10:24:52 PM EDT> <Info> <J2EE> <Undeployed : sample1.0>
<Apr 16, 2001 10:24:53 PM EDT> <Info> <EJB> <EJB Deploying file:
HelloWorldEJB.j
ar>
<Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying EJB Component
: H
elloWorldEJB
weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested
exc
eption is:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a
repl
ica-aware stub to a name that is currently bound to a replica-aware stub;
remain
ing name ''
javax.naming.NameAlreadyBoundException: Can't rebind anything but a
replica-awar
e stub to a name that is currently bound to a replica-aware stub; remaining
name
<<no stack trace available>>
>
<Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying application
sampl
e1.0: Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
>
<Apr 16, 2001 10:24:53 PM EDT> <Error> <Management>
<InvocationTargetException s
etting attribute Deployed on MBean
me:Name=sample1.0,Location=app3,Type=Applicat
ionConfig to value true. Method: public void
weblogic.management.mbeans.custom.A
pplication.setDeployed(boolean) throws
weblogic.management.DeploymentException,w
eblogic.management.UndeploymentException
weblogic.management.DeploymentException: Could not deploy:
'HelloWorldEJB.jar':
JNDI name in use
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
at weblogic.j2ee.Application.deploy(Application.java:167)
at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
at
weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
ation.java:217)
at
weblogic.management.mbeans.custom.Application.setDeployed(Application
.java:187)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
anImpl.java:1136)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
anImpl.java:773)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
anImpl.java:750)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
igurationMBeanImpl.java:256)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1331)
at
weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Remo
teMBeanServerImpl_WLSkel.java:1075)
at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
va:373)
at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
va:237)
at
weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
andler.java:118)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
to b
ind an object under the name HelloWorldHome_EO in the jndi tree. The object
you
have bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is
non
clusterable and you have tried to bind more than once from two or more
servers.
Such objects can only deployed from one server.>
<Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
to b
ind an object under the name HelloWorldHome in the jndi tree. The object you
hav
e bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is non
clu
sterable and you have tried to bind more than once from two or more servers.
Suc
h objects can only deployed from one server.>
Here's a question. Why am I seeing "weblogic.ejb20.EJBDeploymentException"?
As far as I know, I have not installed the EJB2.0 container. Does this get
installed by default with sp1? Also, I quite sure that my deployment
descriptors are correct. Here's my weblogic-ejb-jar.xml for the HelloWorld
EJB:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0
EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorld</ejb-name>
<caching-descriptor>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</caching-descriptor>
<clustering-descriptor>
<home-is-clusterable>true</home-is-clusterable>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
potent>
</clustering-descriptor>
<jndi-name>HelloWorldHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Who needs clustering anyway, damn it?! (Well...I do) Any one know what's
going on here?
This seems like potential redeploy/undeploy bugs. COuld you follow up with
[email protected]
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
Paul Citarella wrote:
> I'm getting an error that I have not seen in the newsgroups so far. It
> happens when I deploy what I believe to be a properly configured clusterable
> application (.ear file) to my cluster.
>
> Here's my setup:
> WebLogic 6.0 sp1, three instances across 2 machines. The admin server (wl1)
> is running on Stimpy (win2kAS) on 10.10.10.21 (it is not part of the
> cluster). The 1st managed server (app1) is also on Stimpy bound to
> 10.10.10.22 (a virtual IP). The second managed server (app3) is on Ren
> (also win2kAS) at 10.10.10.23. Auto-deploy is off. I am using the console
> to deploy the app. (I turned auto-deploy off because the app was getting
> deployed to the admin server automatically and throwing an error because of
> the clustered HTTP session state)
>
> Here's what happens.
>
> I start up all of the instances with no apps deployed. Everything appears
> to be running fine. No errors. I then use the console to deploy my
> application (sample1.0.ear). I select only the cluster as the target for
> the EJB and the webapp. If I try to access the app at this point I just get
> 404's. I then restart all of the servers and the app gets deployed across
> the cluster with no errors. I can access everything JSPs, servlets, and an
> EJB without issue.
>
> My problem comes when I try to re-deploy the application. I have tried this
> using the console, and by copying the new .ear file to the applications
> directory on the admin server. I always get the same error, and it only
> shows up on "app1" the first managed server in the cluster. Below is the
> output form the log:
>
> Undeploying EJB Component HelloWorldEJB
> <Apr 16, 2001 10:24:52 PM EDT> <Info> <J2EE> <Undeployed : sample1.0>
> <Apr 16, 2001 10:24:53 PM EDT> <Info> <EJB> <EJB Deploying file:
> HelloWorldEJB.j
> ar>
> <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying EJB Component
> : H
> elloWorldEJB
> weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested
> exc
> eption is:
> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
> repl
> ica-aware stub to a name that is currently bound to a replica-aware stub;
> remain
> ing name ''
> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
> replica-awar
> e stub to a name that is currently bound to a replica-aware stub; remaining
> name
> ''
> <<no stack trace available>>
> >
> <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying application
> sampl
> e1.0: Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
> >
> <Apr 16, 2001 10:24:53 PM EDT> <Error> <Management>
> <InvocationTargetException s
> etting attribute Deployed on MBean
> me:Name=sample1.0,Location=app3,Type=Applicat
> ionConfig to value true. Method: public void
> weblogic.management.mbeans.custom.A
> pplication.setDeployed(boolean) throws
> weblogic.management.DeploymentException,w
> eblogic.management.UndeploymentException
> weblogic.management.DeploymentException: Could not deploy:
> 'HelloWorldEJB.jar':
> JNDI name in use
>
> at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
> at weblogic.j2ee.Application.deploy(Application.java:167)
> at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
> at
> weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
> ation.java:217)
> at
> weblogic.management.mbeans.custom.Application.setDeployed(Application
> .java:187)
> at java.lang.reflect.Method.invoke(Native Method)
> at
> weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
> anImpl.java:1136)
> at
> weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
> anImpl.java:773)
> at
> weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
> anImpl.java:750)
> at
> weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
> igurationMBeanImpl.java:256)
> at
> com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
> ava:1356)
> at
> com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
> ava:1331)
> at
> weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Remo
> teMBeanServerImpl_WLSkel.java:1075)
> at
> weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
> va:373)
> at
> weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
> va:237)
> at
> weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
> andler.java:118)
> at
> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
> .java:17)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >
> <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
> to b
> ind an object under the name HelloWorldHome_EO in the jndi tree. The object
> you
> have bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is
> non
> clusterable and you have tried to bind more than once from two or more
> servers.
> Such objects can only deployed from one server.>
> <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
> to b
> ind an object under the name HelloWorldHome in the jndi tree. The object you
> hav
> e bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is non
> clu
> sterable and you have tried to bind more than once from two or more servers.
> Suc
> h objects can only deployed from one server.>
>
> Here's a question. Why am I seeing "weblogic.ejb20.EJBDeploymentException"?
> As far as I know, I have not installed the EJB2.0 container. Does this get
> installed by default with sp1? Also, I quite sure that my deployment
> descriptors are correct. Here's my weblogic-ejb-jar.xml for the HelloWorld
> EJB:
>
> <?xml version="1.0"?>
> <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0
> EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
> <weblogic-ejb-jar>
> <weblogic-enterprise-bean>
> <ejb-name>HelloWorld</ejb-name>
> <caching-descriptor>
> <max-beans-in-free-pool>100</max-beans-in-free-pool>
> </caching-descriptor>
> <clustering-descriptor>
> <home-is-clusterable>true</home-is-clusterable>
> <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
> <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
> potent>
> </clustering-descriptor>
> <jndi-name>HelloWorldHome</jndi-name>
> </weblogic-enterprise-bean>
> </weblogic-ejb-jar>
>
> Who needs clustering anyway, damn it?! (Well...I do) Any one know what's
> going on here?
Similar Messages
-
Whats the best way to get the server name in a servlet deployed to a cluster?
Hi,
I have a servlet in a web application that is deployed to a cluster, just
wondering what is the best way to get the name of the node that the server is
running on at run time??
Thanks
Please try to modify the following code and test for your purpose: (check Weblogic
class document for detail)
import javax.naming.*;
import weblogic.jndi.*;
import weblogic.management.*;
import weblogic.management.configuration.*;
import weblogic.management.runtime.*;
MBeanHome home = null;
try{
//The Environment class represents the properties used to create
//an initial Context. DEfault constructor constructs an Environment
//with default properties, that is, with a WebLogic initial context.
//If unset, the properties for principal and credentials default to
//guest/guest, and the provider URL defaults to "t3://localhost:7001".
Environment env = new Environment();
//Sets the Context.PROVIDER_URL property value to the value of
//the argument url.
if(admin_url!=null){
env.setProviderUrl(admin_url);
//Sets the Context.SECURITY_PRINCIPAL property to the value of
//the argument principal.
env.setSecurityPrincipal(username);
//Sets the value of the Context.SECURITY_CREDENTIAL property to
//the value of the argument cedentials
env.setSecurityCredentials(password);
//Returns an initial context based on the properties in an Environment.
ctx = env.getInitialContext();
}else ctx = new InitialContext();
home = (MBeanHome) ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
ctx.close(); //free resource
// or if looking up a specific MBeanHome
//home = (MBeanHome) ctx.lookup(MBeanHome.JNDI_NAME + "." + serverName);
DomainMBean dmb = home.getActiveDomain(); //Get Active Domain
ServerMBean[] sbeans = dmb.getServers(); //Get all servers
if(sbeans!=null){
for(int s1=0; s1<sbeans.length; s1++){
String privip = sbeans[s1].getListenAddress();
sbeans[s1].getName();
sbeans[s1].getListenPort();
WebServerMBean wmb = sbeans[s1].getWebServer();
}catch(Exception ex){
"Gao Jun" <[email protected]> wrote:
>Is there any sample code? Thanks
>
>Best Regards,
>Jun Gao
>
>"Xiang Rao" <[email protected]> wrote in message
>news:[email protected]...
>>
>> Sure. You can use the Weblogic management APIs to query ServerBean.
>>
>>
>> "Me" <[email protected]> wrote:
>> >
>> >Thanks for your reply, i was hoping to find a better way for example
>> >a class in
>> >weblogic API.
>> >
>> >Thanks
>> >
>> >"Xiang Rao" <[email protected]> wrote:
>> >>
>> >>Physical: InetAddress.getLocalHost().getHostName()
>> >>Weblogic: System.getProperty("weblogic.Name");
>> >>
>> >>
>> >>"Me" <[email protected]> wrote:
>> >>>
>> >>>Hi,
>> >>> I have a servlet in a web application that is deployed to a
>cluster,
>> >>>just
>> >>>wondering what is the best way to get the name of the node that
>the
>> >>server
>> >>>is
>> >>>running on at run time??
>> >>>
>> >>>Thanks
>> >>
>> >
>>
>
>
-
Exception during application deployment
Hi all,
I'm trying to deploy a wd application from NWDS (NW2004 sp19) and I get an error:
The application references the following jars - com.sap.security.api, com.sap.security.api.ep5, bc.rf.framework_api and bc.util.public_api. I also defined a Sharing Reference - "PORTAL:sap.com/com.sap.km.application".
Full error stacktrace:
06/10/2008 10:20:25 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[007]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7186 - 630]/>
<!NAME[D:\usr\sap\EPT\JC00\SDM\program\log\sdmcl20081006082023.log]/>
<!PATTERN[sdmcl20081006082023.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1255]/>
<!LOGHEADER[END]/>
Oct 6, 2008 10:20:23 AM Info: -
Starting deployment -
Oct 6, 2008 10:20:23 AM Info: Error handling strategy: OnErrorStop
Oct 6, 2008 10:20:23 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Oct 6, 2008 10:20:23 AM Info: Update strategy: UpdateAllVersions
Oct 6, 2008 10:20:23 AM Info: Starting deployment prerequisites:
Oct 6, 2008 10:20:23 AM Info: Loading selected archives...
Oct 6, 2008 10:20:23 AM Info: Loading archive 'D:\usr\sap\EPT\JC00\SDM\program\temp\temp86DepthVisit.ear'
Oct 6, 2008 10:20:24 AM Info: Selected archives successfully loaded.
Oct 6, 2008 10:20:24 AM Info: Actions per selected component:
Oct 6, 2008 10:20:24 AM Info: Update: Selected development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0' updates currently deployed development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.09.25.15.49.17'/'0'.
Oct 6, 2008 10:20:24 AM Info: Ending deployment prerequisites. All items are correct.
Oct 6, 2008 10:20:24 AM Info: Saved current Engine state.
Oct 6, 2008 10:20:24 AM Info: Starting: Update: Selected development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0' updates currently deployed development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.09.25.15.49.17'/'0'.
Oct 6, 2008 10:20:24 AM Info: SDA to be deployed: D:\usr\sap\EPT\JC00\SDM\root\origin\local\DepthVisit\LOKAL\0\0.2008.10.06.10.20.19\temp86DepthVisit.ear
Oct 6, 2008 10:20:24 AM Info: Software type of SDA: J2EE
Oct 6, 2008 10:20:24 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 6, 2008 10:20:24 AM Info: Begin of log messages of the target system:
08/10/06 10:20:24 - ***********************************************************
08/10/06 10:20:24 - Start updating EAR file...
08/10/06 10:20:24 - start-up mode is lazy
08/10/06 10:20:24 - EAR file updated successfully for 63ms.
08/10/06 10:20:24 - Start updating...
08/10/06 10:20:24 - EAR file uploaded to server for 79ms.
08/10/06 10:20:24 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application local/DepthVisit..
Reason: Exception during generation of components of application local/DepthVisit in container webdynpro.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployApplicationDuringUpdate(DeployServiceImpl.java:701)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:666)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
... 12 more
Caused by: java.lang.NullPointerException
at com.sap.engine.services.webdynpro.util.Procedures.switchio(Procedures.java:40)
at com.sap.engine.services.webdynpro.ArchiveParser.extractEntry(ArchiveParser.java:127)
at com.sap.engine.services.webdynpro.ArchiveParser.process(ArchiveParser.java:101)
at com.sap.engine.services.webdynpro.PApplication.process(PApplication.java:170)
at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:838)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 18 more
For detailed information see the log file of the Deploy Service.
08/10/06 10:20:24 - ***********************************************************
Oct 6, 2008 10:20:24 AM Info: End of log messages of the target system.
Oct 6, 2008 10:20:24 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 6, 2008 10:20:24 AM Error: Aborted: development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application local/DepthVisit..
Reason: Exception during generation of components of application local/DepthVisit in container webdynpro.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 6, 2008 10:20:24 AM Info: Starting to save the repository
Oct 6, 2008 10:20:25 AM Info: Finished saving the repository
Oct 6, 2008 10:20:25 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Oct 6, 2008 10:20:25 AM Error: -
At least one of the Deployments failed -Hi,
Building the ear file is not the problem.
The deployment fails.
Seems that somehow I dont have those jars on the server.....
Aviad
Edit: I've done a search on the server and all the relevant jars are there, none is missing.
Whats next?
Edited by: Aviad Levy on Oct 6, 2008 4:41 PM -
JMS sub-deployment targeted to cluster
Hello,
I have read at the Oracle documentation that we can use a sub-deployment within a JMS module targeted only to a single JMS Server. But I have an application that create JMS resources with deploy descriptors (Application modules) and target the sub-deployment to a cluster with two machines, each machine has a JMSServer. It seems to work (I see them on the JNDI tree on both machines). This is the jms.xml:
Do you also use sub-deployment targeted to a cluster or I shouldn't? Thank you in advance ;)
I am using webLogic version 10.3.4.0
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-jms xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-jms"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
<wls:quota name="InboundMessageQuota">
<wls:bytes-maximum>1000000</wls:bytes-maximum>
<wls:messages-maximum>10000</wls:messages-maximum>
</wls:quota>
<!-- Factories -->
<wls:connection-factory name="InboundMessageConnectionFactory">
<wls:sub-deployment-name>InboundMessage</wls:sub-deployment-name>
<wls:jndi-name>jms.InboundMessageConnectionFactory</wls:jndi-name>
<wls:security-params>
<wls:attach-jmsx-user-id>false</wls:attach-jmsx-user-id>
</wls:security-params>
</wls:connection-factory>
<!-- Queue's -->
<wls:uniform-distributed-queue name="InboundMessageQueue">
<wls:sub-deployment-name>InboundMessage</wls:sub-deployment-name>
<wls:delivery-params-overrides>
<wls:delivery-mode>Non-Persistent</wls:delivery-mode>
</wls:delivery-params-overrides>
<wls:delivery-failure-params>
<wls:redelivery-limit>0</wls:redelivery-limit>
</wls:delivery-failure-params>
<wls:jndi-name>jms.InboundMessageQueue</wls:jndi-name>
</wls:uniform-distributed-queue>
</wls:weblogic-jms>Technically, cluster targeting a distributed destination is supported, and it'll work as long as your can be absolutely assured that the cluster will never host additional JMS servers - perhaps from future projects, or due to integrating third party products. Otherwise, your distributed destinations will end up creating instances on JMS servers where they don't belong - a common mistake that can be tough to diagnose and untangle. I highly recommend staying with the best practice of using a subdeployment that references exactly the intended JMS servers. Note that a subdeployment can reference more than one JMS server.
See [url http://download.oracle.com/docs/cd/E17904_01/web.1111/e13738/best_practice.htm#JMSAD455] WL JMS Configuration Best Practices
Hope this helps,
Tom -
Jndi exception using weblogic.Admin
I was trying out the commands offered by weblogic.Admin to manage the packaged petstore server. I tried the following command and got jndi exception (null):
command:java weblogic.Admin -url petstoreServer.com:7001 GET -pretty -type Server
Error:Exception in thread "main" java.lang.IllegalArgumentException: JNDI naming exception: null
at weblogic.management.commandline.CommandLine.findMBeanHome(CommandLine.java:460)
at weblogic.management.commandline.CommandLine.doCommandline(CommandLine.java:86)
at weblogic.management.commandline.CommandLine.<init>(CommandLine.java:69)
at weblogic.Admin.main(Admin.java:689)
I checked in the console. A jndi name for petstoreServer does exist.The current WebLogic 6.0 Beta-1 documentation incorrectly specifies the following in its example.
java weblogic.Admin -url xyz.com:7001 GET -pretty -type Server
This example falsely gives the impression that you must append ".com" to your host name. We will correct the document in the next revision to look like:
java weblogic.Admin -url hrserver:7001 GET -pretty -type Server
The -url petstoreServer.com:7001 parameter is incorrect. The command requires you to specify the <HostName>:<PortNumber> for the -url parameter.
Regards,
-Sachin
Helen Semus wrote:
I was trying out the commands offered by weblogic.Admin to manage the packaged petstore server. I tried the following command and got jndi exception (null):
command:java weblogic.Admin -url petstoreServer.com:7001 GET -pretty -type Server
Error:Exception in thread "main" java.lang.IllegalArgumentException: JNDI naming exception: null
at weblogic.management.commandline.CommandLine.findMBeanHome(CommandLine.java:460)
at weblogic.management.commandline.CommandLine.doCommandline(CommandLine.java:86)
at weblogic.management.commandline.CommandLine.<init>(CommandLine.java:69)
at weblogic.Admin.main(Admin.java:689)
I checked in the console. A jndi name for petstoreServer does exist.--
Sachin Thatte, Senior Software Engineer
BEA Systems, Inc
WWW: http://www.bea.com
[att1.html] -
Exception recieved from deployment driver
hi all,
I have added axis2 services in a portal pproject.After that I am gettin exception.I tried without adding axis2 in project facets.It waas fine..
But after adding axis2 ..and tried to a portal or anything.it is showin the following exception
Module named 'Ear' failed to deploy. See Error Log view for more detail.
Deployment connection was released before the state of deployment was known.[Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Ear on AdminServer.: [HTTP:101216]Servlet: "AxisAdminServlet" failed to preload on startup in Web application: "portal".
org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing
at org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:464)
at org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(AxisConfiguration.java:591)
at org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:615)
at org.apache.axis2.deployment.WarBasedAxisConfigurator.engageGlobalModules(WarBasedAxisConfigurator.java:301)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:81)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436)
at org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.java:55)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1899)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1873)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1791)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3005)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Exception received from deployment driver. See Error Log view for more detail.Look at the Apache Axis2 docs for weblogic.
I had to include a file modules.list under WB-INF/modules , which contains the mar file names.
It is in the docs, it might help you?
It did work for me on deploying Business Objects wars
Edited by: user11979032 on May 20, 2011 1:29 AM -
Accessing JMS UDD deployed on OSB cluster from a composite JMS adapter deployed on soa cluster
Our environment setup
Single domain with three clusters
osb_cluster.soa_cluster and bam_cluster
osb_cluster: osb_server1 and osb_server2
wlsbJMSServer_auto_1: targetted to osb_server1
wlsbJMSServer_auto_2: targetted to osb_server2
osb_subdeployment1:targetted to wlsbJMSServer_auto_1 and wlsbJMSServer_auto_2 JMS servers
osb_subdeployment1 has JMS UDD queue jms/wlsb/queue
soa_cluster: soa_server1 and soa_server2
There is a BPEL composite deployed to soa_cluster. It has JMS adapter trying to read messages from jms/wlsb/queue
JCA JMSAdapter is deployed to osb,soa clusters and Admin server
ConnectionFactory is targetted to soa and osb clusters (osb_cluster and soa_cluster)
We have bounced soa and osb servers(not admin) after jms changes.
soa log says
JMSAdapter Composite1l JmsDDEndpoint_onFailure: Unable to resolve 'jms.wlsb.queue. Resolved 'jms'
Can we access JMS destinations deployed on one cluster from different cluster?
If yes, how can we do that ? do we need to modify BPEL JCA file to indicate destination is on another cluster?
Thanks,
PraveenAnybody has faced similar issue?
-
JNDI Exception : [System] not bound in naming services
Hi All,
Is there any way to resolve this JNDI exception "Invalid Path: [System/Launchers] not bound in naming service" ?
Thanks in AdvanceThis did not work dear. I assume when you say [Add ur datasource], you mean the name of the datasource, and I did as you told. I was wondering though that I have an independent java class which try to get data source from WSAD server, then how does web.xml help, may be I am not understanding the connection here.
Just to let you know, that same java class gets the datasource from 4.0 test server. I am running both servers now i.e. 4.0 test and 5.0 test server on different ports, and only data source from 4.0 workd good. Do you have any other solution, which I can try.
Is there any difference the way data source is accessed between 4.0 and 5.0 versions.
Thanks in advance.
Open web.xml, There will reference tab,, then take
Resource, Add ur datasourse on where the Cursor points
and then JNDI Name.
U need to restart .. -
Hi,
I'm using Weblogic Server 9.2. I'm having problems to deploy a .ear aplication.?:|
When I try to install the aplication i get the following error:
javax.enterprise.deploy.spi.exceptions.InvalidModuleException: [J2EE Deployment SPI:260105]Failed to create DDBeanRoot for application, 'sgi-core-1.0.jar'
Could anyone say me how can I solve this error?
The deployment descriptor weblogic-ejb-jar.xml seems to be correct.
I'm using Andromda to generate the .ear file, so I don't know if it can be causing any problems
If anyone could help me...
Thanks in advanceHi,
The J2EE Error code siply suggest that there is something wrong in your Deployment Descriptors...
Can u please post the XML files available inside your "WEB-INF" directory?
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here) -
Hi,
I have a bea cluster configured among two physical servers
First machine has the admin server configured. It also has a managed server configured in the cluster named "cluster" . The application ear file is copied on to this server only (No shared storage is available)
second machine has one managed server configured in the same cluster "cluster"
When I have done the deployment onto the "cluster" everything worked fine. I am able to access the applicatio through both the managed server's urls.
Then for testing purpose, I shutdown the first server which has the admin server. Still the application continued to work on the second server
Then I have restarted the managed server on the second machine by keeping the first machine shutdown, the managed server started in ADMIN mode, and is refusing the application requests.
can anyone suggest any workaround ??
Thanks
Ushas SymonHi,
1)start the adminserver
2)restart the secondary server
-Paul -
JNDI Exception on Cluster Redeployment
"Does anyone know what was the resolution on the attached newsgroup posting? i am experiencing a similar
Jerry Davis <[email protected]> wrote:
>"Does anyone know what was the resolution on the attached newsgroup posting?
> i am experiencing a similar
This seems to have gotten chopped. I am seeing the following error when attempting
to hot-deploy (through the admin console) a simple stateless EJB
to the second managed server, and receive this exception. The first managed server
receives the deployment no problem; it's only the second managed
server that throws the exception.
<Jun 14, 2001 4:56:39 PM CDT> <Error> <J2EE> <Error deploying application HelloWorld_EJB:
Could not deploy: 'HelloWorld_EJB.jar': JNDI name in use
>
<Jun 14, 2001 4:56:39 PM CDT> <Error> <Management> <InvocationTargetException
setting attribute Deployed on MBean wwt:Name=HelloWorld_EJB,Location=testlogic2Server,Type=ApplicationConfig
to value true. Method: public void weblogic.management.mbeans.custom.Application.setDeployed(boolean)
throws weblogic.management.DeploymentException,weblogic.management.UndeploymentException
weblogic.management.DeploymentException: Could not deploy: 'HelloWorld_EJB.jar':
JNDI name in use
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
at weblogic.j2ee.Application.deploy(Application.java:167)
at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:217)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:187)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1136)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:773)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:750)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:256)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBeanServerImpl_WLSkel.java:1075)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Jun 14, 2001 4:56:39 PM CDT> <Error> <Cluster> <Conflict start: You tried to
bind an object under the name HelloWorldBean_EO in the jndi tree. The object you
have bound weblogic.rmi.cluster.ClusterableRemoteObject from prodlogic2 is non
clusterable and you have tried to bind more than once from two or more servers.
Such objects can only deployed from one server.>
-
JNDI not found deploy bpel in cluster
Hi I have this problem:
I install BPEL CLuster in two hosts: mtier01 and mtier02 and I have a lbr (balancer) in front of this servers (mtier01 and 02).
I deploy bpel using bpel console and I get a error:
JNDI not found.
I read log: log.xml of bpel, and it tell me:
port request of opmn not open of lbr, i need change configuration of host and port opmn for mtier01 and mtier02 (it is open in this hosts).
I don´t now why bpel or OC4J_SOA need port opmn of lbr01 (not safe, i can´t open).
If i use ANT i tell which host and port need for deploy.
* j2ee.hostname
*opmn.requestport
*http.hostaname
What can i do in the configuration of bpel for resolve tis problem?
Thanks.
MaximilianoHow i you installe the cluster, followed the documentation?
http://download.oracle.com/docs/cd/B31017_01/core.1013/b28941/soa.htm
Marc -
Error while deploying on a cluster
Hi all,
when I deploy my WebApp on a cluster I recieved the following error:
####<Dec 13, 2006 5:18:14 PM CET> <Debug> <Deployer> <eb0bzl58> <admdwsgem> <ExecuteThread: '0' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ManagementException: weblogic.management.DeploymentException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NullPointerException]
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:730)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>
WebLogic version is 8.1 sp6
My WebApp uses Apache Struts and OJB
Could anyone help me on this problem?
Thanks and sorry for my EnglishHi all,
Any help?
Thanks -
SecurityException when deploying to a cluster.Please help !
Hi Guys,
I am running a clustering scenario wherein i have an administration server and 2 managed servers(this forms the cluster). Admin server and 1 managed server is in one machine and the second managed server is in another machine.Node Manager is configured in both the machines.
I am able to get a successful application deployment when i choose to deploy it partially to either of the manged servers in the cluster.But when i choose to deploy the application to the whole cluster i always get the following exception indicating that the run-as principal 'ProcessInjectorMessageBeanUser' is not a member of the current security realm.However, in the secuity realm that this domain is using,i can see this user listed in the Administration console.Any idea what could be wrong ?
As i am beginner in weblogic clustering, Any help will be really appreciated.
[Deployer:149033]preparing application COM-ORCH-expand-1.1 on grp-fred
[Deployer:149033]preparing application COM-ORCH-expand-1.1 on new_managedServer_1
[Deployer:149033]prepared application COM-ORCH-expand-1.1 on grp-fred
[Deployer:149033]failed application COM-ORCH-expand-1.1 on new_managedServer_1
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application COM-ORCH-expand-1.1 on TFFCluster.:
Exception:weblogic.management.ApplicationException: prepare failed for ORCH-ejb-1.1.jar
Module: ORCH-ejb-1.1.jar Error: Exception preparing module: EJBModule(ORCH-ejb-1.1.jar,status=NEW)
Unable to deploy EJB: .\new_managedServer_1\stage\COM-ORCH-expand-1.1\ORCH-ejb-1.1.jar from ORCH-ejb-1.1.jar:
weblogic.ejb20.WLDeploymentException: The run-as principal 'ProcessInjectorMessageBeanUser' for EJB 'com/OrchestratorMessageBean' is not a user in the current realm. The user must exist for the EJB to successfully deploy.
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.getRunAsPrincipal(MBeanDeploymentInfoImpl.java:1047)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeRunAsSettings(MBeanDeploymentInfoImpl.java:838)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:246)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Cheers,
JoshCan you post the config.xml from both boxes ?
I think there may some mismatch in the Advanced Security Credentials on both domains.
Dips -
Error when deploy to weblogic cluster
My cluster has 2 servers A, B. when I deploy an WebCenter Custom Portal application to weblogic cluster, application on server A work well and application on server B is failed. Log on failed server is “what do i do: seems an odd quirk of the EJB spec. The exception is:java.lang.NoClassDefFoundError: Oracle/jdeveloper/db/adapter/DatabaseProvider”
When I reconfig cluster and then deploy, application on server B work well but application on server A is failed.
Please advise what should I do in this situation?Hi,
It seems your Application is running with non-seralizable objects where non-searlizable are not supported on cluster environment.
Please check server logs whether you have such warning messages are not.
Let me know if you need any further help on this issue.
Regards,
Kal
Maybe you are looking for
-
Reg: Context mapping.
Hi All, When we do mapping of value nodes ,there in properties we have a property called mapping type. It has 3 options 1) collection and selection 2) collection only 3)not applicable . what is this property? Thanks in advance.
-
Will satellite coverage of Germany in Maps be updated to show areas without clouds?
Hi, while scanning through the ios6 Maps app, for greater parts of Germany I found that the satellite coverage shows LOTS of clouds, obstructing the view. That way the satellite or hybrid views in Maps isn't useable. Does anybody know if there is a s
-
Hi, I want to understand the licensing structure of Microsoft windows 2008 server standard edition. If i buy a Microsoft windows 2008 server standard edition license ,can i activate the IIS in that without any extra cost involved ? Can i use this lic
-
HT1296 syncing from computer to phone
1. Why does my iPhone 4 not show up on My Computer as a Device? And yet it beeps accordingly, and iTunes starts up, so I must be connected? 2. I want to move music from my computer onto my iPhone, but sync'ing does nothing, as though I am not conn
-
Humming sound coming from speaker output
I did create a discussion on this before, but can't find it anywhere. I have a Mac Pro 4,1 and recently noticed a humming sound on my wireless headphones. I thought it might be other wireless products interfiering with the headphone. However when I c