Stateful session bean deploying
Hello,
I try to deploy stateful SessionBean with WL 6.0.
Content of my 'weblogic-ejb-jar.xml' file is:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0
EJB//EN' 'http://www.bea.com/servers/wls60/ejb20/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HashtableSessionBean</ejb-name>
<stateful-session-descriptor>
<stateful-session-clustering>
<home-is-clusterable>true</home-is-clusterable>
<replication-type>InMemory</replication-type>
</stateful-session-clustering>
</stateful-session-descriptor>
<jndi-name>HashtableSessionBean</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
But I still recive error like bellow:
####<2001-03-28 18:15:15 GMT+02:00> <Error> <J2EE> <clikra003> <myserver>
<Application Manager Thread> <> <> <160002> <Error deploying EJB Component :
HashtableSessionBean>
weblogic.ejb20.EJBDeploymentException: Exception in EJB Deployment; nested
exception is:
javax.naming.NamingException [Root exception is java.rmi.MarshalException:
failed to marshal public abstract void
weblogic.jndi.internal.NamingNode.rebind(java.lang.String,java.lang.Object,j
ava.util.Hashtable) throws
javax.naming.NamingException,java.rmi.RemoteException; nested exception is:
java.rmi.server.ExportException: Failed to invoke contructor for
RuntimeDescriptor: class weblogic.rmi.internal.BasicRuntimeDescriptor;
nested exception is:
java.lang.reflect.InvocationTargetException]
javax.naming.NamingException. Root exception is java.rmi.MarshalException:
failed to marshal public abstract void
weblogic.jndi.internal.NamingNode.rebind(java.lang.String,java.lang.Object,j
ava.util.Hashtable) throws
javax.naming.NamingException,java.rmi.RemoteException; nested exception is:
java.rmi.server.ExportException: Failed to invoke contructor for
RuntimeDescriptor: class weblogic.rmi.internal.BasicRuntimeDescriptor;
nested exception is:
java.lang.reflect.InvocationTargetException
java.rmi.server.ExportException: Failed to invoke contructor for
RuntimeDescriptor: class weblogic.rmi.internal.BasicRuntimeDescriptor;
nested exception is:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError:
weblogic/common/managedobject/JavaRemoteManageable
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
at
weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLo
ader.java:304)
at
weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.
java:155)
at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
at weblogic.rmi.utils.Utilities.classForName(Utilities.java:209)
at weblogic.rmi.internal.BasicDescriptor.<init>(BasicDescriptor.java:88)
at weblogic.rmi.internal.BasicDescriptor.<init>(BasicDescriptor.java:141)
at
weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.j
ava:59)
at java.lang.reflect.Constructor.newInstance(Native Method)
at
weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManager.java:
81)
at
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java
:39)
at
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java
:30)
at
weblogic.rmi.internal.OIDManager.getRequestDispatcher(OIDManager.java:279)
at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:268)
at weblogic.rmi.internal.OIDManager.replaceObject(OIDManager.java:96)
at
weblogic.common.internal.WLObjectOutputStreamBase2.replaceObject(WLObjectOut
putStreamBase2.java:47)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:323)
at
weblogic.rmi.internal.CBVOutputStream.writeObjectInternal(CBVOutputStream.ja
va:220)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:213)
at
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:190)
at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:19)
at
weblogic.rmi.internal.BasicRemoteRef.marshalArgs(BasicRemoteRef.java:121)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:246)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:225)
at
weblogic.jndi.internal.ServerNamingNode_WLStub.rebind(ServerNamingNode_WLStu
b.java:502)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:123)
at weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:117)
at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
Impl.java:483)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1105)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:908)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
at weblogic.j2ee.Application.addComponent(Application.java:126)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:283)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:109)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:562)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
48)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(Confi
gurationMBeanImpl.java:409)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:287)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
.java:866)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
.java:853)
at
weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:566)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
48)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy8.addTarget(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
anager.java:486)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
ionManager.java:557)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
ionManager.java:504)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
.java:428)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
.java:380)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
er.java:152)
at
weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(A
pplicationManager.java:643)
####<2001-03-28 18:15:15 GMT+02:00> <Error> <J2EE> <clikra003> <myserver>
<Application Manager Thread> <> <> <160001> <Error deploying application
HashtableSessionBean: Could not deploy: 'HashtableSessionBean.jar'
Possible reasons include:
1. The bean or an interface class has been modified but
the deployment descriptor has not been updated
2. The database mappings in the deployment descriptor do not
match the database definition
3. The jar file is not a valid jar file
4. The jar file does not contain a valid bean>
Robert
Hello,
<stateful-session-clustering>
<replication-type>InMemory</replication-type>
</stateful-session-clustering>
Statement above belongs to 'weblogic-ejb-jar.xml' and it is right in my
opinion.
I have another one statement describing SessionBean which deploy it as
stateful bean (it is 'ejb-jar.xml' file):
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>HashtableSessionBean</ejb-name>
<home>com.usermgmt.sessionbeans.hashtable.HashtableSessionHome</home>
<remote>com.usermgmt.sessionbeans.hashtable.HashtableSession</remote>
<ejb-class>com.usermgmt.sessionbeans.hashtable.HashtableSessionBean</ejb-cla
ss>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
I think that everything should go right, but SessionBean is not replicated.
Where is the problem?
Robert
Uzytkownik "Prasad Peddada" <[email protected]> napisal w wiadomosci
news:[email protected]...
> Its not stateful session descriptor from your xml file instead it is
> stateful-session-clustering according to the docs.
>
> -- Prasad
>
> ps: For ejb questions you will get better answers if you post to ejb
newsgroup.
>
>
> <stateful-session-clustering>
>
>
> ...
>
>
> <replication-type>InMemory</replication-type>
>
>
> </stateful-session-clustering>
>
>
> Robert Zaczynski wrote:
>
> > Thanks for help. I resolved this problem but my Stateful SessionBean
doesn't
> > replicate.
> > Have I to use any special statement or settings???
> >
> > Robert
> >
> > Uzytkownik "Prasad Peddada" <[email protected]> napisal w
wiadomosci
> > news:[email protected]...
> > > Did you modify the weblogic specific deployment descriptor xml file
after
> > > running ejbc. If so, you should run ejbc again and then jar it up
again
> > and
> > > trying deploying and your problem should go away.
> > >
> > >
> > > Cheers
> > >
> > > -- Prasad
> > >
> > > "Robert Zaczyñski" wrote:
> > >
> > > > Hello,
> > > >
> > > > I try to deploy stateful SessionBean with WL 6.0.
> > > >
> > > > Content of my 'weblogic-ejb-jar.xml' file is:
> > > >
> > > > <?xml version="1.0"?>
> > > >
> > > > <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD
WebLogic
> > 6.0.0
> > > > EJB//EN'
> > 'http://www.bea.com/servers/wls60/ejb20/dtd/weblogic-ejb-jar.dtd'>
> > > > <weblogic-ejb-jar>
> > > > <weblogic-enterprise-bean>
> > > > <ejb-name>HashtableSessionBean</ejb-name>
> > > >
> > > > <stateful-session-descriptor>
> > > > <stateful-session-clustering>
> > > > <home-is-clusterable>true</home-is-clusterable>
> > > > <replication-type>InMemory</replication-type>
> > > > </stateful-session-clustering>
> > > > </stateful-session-descriptor>
> > > >
> > > > <jndi-name>HashtableSessionBean</jndi-name>
> > > >
> > > > </weblogic-enterprise-bean>
> > > > </weblogic-ejb-jar>
> > > >
> > > > But I still recive error like bellow:
> > > >
> > > > ####<2001-03-28 18:15:15 GMT+02:00> <Error> <J2EE> <clikra003>
> > <myserver>
> > > > <Application Manager Thread> <> <> <160002> <Error deploying EJB
> > Component :
> > > > HashtableSessionBean>
> > > > weblogic.ejb20.EJBDeploymentException: Exception in EJB Deployment;
> > nested
> > > > exception is:
> > > > javax.naming.NamingException [Root exception is
> > java.rmi.MarshalException:
> > > > failed to marshal public abstract void
> > > >
> >
weblogic.jndi.internal.NamingNode.rebind(java.lang.String,java.lang.Object,j
> > > > ava.util.Hashtable) throws
> > > > javax.naming.NamingException,java.rmi.RemoteException; nested
exception
> > is:
> > > > java.rmi.server.ExportException: Failed to invoke contructor for
> > > > RuntimeDescriptor: class
weblogic.rmi.internal.BasicRuntimeDescriptor;
> > > > nested exception is:
> > > > java.lang.reflect.InvocationTargetException]
> > > > javax.naming.NamingException. Root exception is
> > java.rmi.MarshalException:
> > > > failed to marshal public abstract void
> > > >
> >
weblogic.jndi.internal.NamingNode.rebind(java.lang.String,java.lang.Object,j
> > > > ava.util.Hashtable) throws
> > > > javax.naming.NamingException,java.rmi.RemoteException; nested
exception
> > is:
> > > > java.rmi.server.ExportException: Failed to invoke contructor for
> > > > RuntimeDescriptor: class
weblogic.rmi.internal.BasicRuntimeDescriptor;
> > > > nested exception is:
> > > > java.lang.reflect.InvocationTargetException
> > > > java.rmi.server.ExportException: Failed to invoke contructor for
> > > > RuntimeDescriptor: class
weblogic.rmi.internal.BasicRuntimeDescriptor;
> > > > nested exception is:
> > > > java.lang.reflect.InvocationTargetException
> > > > java.lang.reflect.InvocationTargetException:
> > java.lang.NoClassDefFoundError:
> > > > weblogic/common/managedobject/JavaRemoteManageable
> > > > at java.lang.ClassLoader.defineClass0(Native Method)
> > > > at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
> > > > at
> > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
> > > > at
> > > >
> >
weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLo
> > > > ader.java:304)
> > > > at
> > > >
> >
weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.
> > > > java:155)
> > > > at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
> > > > at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
> > > > at weblogic.rmi.utils.Utilities.classForName(Utilities.java:209)
> > > > at
> > weblogic.rmi.internal.BasicDescriptor.<init>(BasicDescriptor.java:88)
> > > > at
> > weblogic.rmi.internal.BasicDescriptor.<init>(BasicDescriptor.java:141)
> > > > at
> > > >
> >
weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.j
> > > > ava:59)
> > > > at java.lang.reflect.Constructor.newInstance(Native Method)
> > > > at
> > > >
> >
weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManager.java:
> > > > 81)
> > > > at
> > > >
> >
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java
> > > > :39)
> > > > at
> > > >
> >
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java
> > > > :30)
> > > > at
> > > >
> >
weblogic.rmi.internal.OIDManager.getRequestDispatcher(OIDManager.java:279)
> > > > at
weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:268)
> > > > at
weblogic.rmi.internal.OIDManager.replaceObject(OIDManager.java:96)
> > > > at
> > > >
> >
weblogic.common.internal.WLObjectOutputStreamBase2.replaceObject(WLObjectOut
> > > > putStreamBase2.java:47)
> > > > at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:323)
> > > > at
> > > >
> >
weblogic.rmi.internal.CBVOutputStream.writeObjectInternal(CBVOutputStream.ja
> > > > va:220)
> > > > at
> > > >
> >
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:213)
> > > > at
> > > >
> >
weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:190)
> > > > at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:19)
> > > > at
> > > >
> >
weblogic.rmi.internal.BasicRemoteRef.marshalArgs(BasicRemoteRef.java:121)
> > > > at
> > > >
> >
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
> > > > :246)
> > > > at
> > > >
> >
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
> > > > :225)
> > > > at
> > > >
> >
weblogic.jndi.internal.ServerNamingNode_WLStub.rebind(ServerNamingNode_WLStu
> > > > b.java:502)
> > > > at
weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:123)
> > > > at
weblogic.jndi.internal.WLContextImpl.rebind(WLContextImpl.java:117)
> > > > at
> > > >
> >
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
> > > > Impl.java:483)
> > > > at
> > weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1105)
> > > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:908)
> > > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
> > > > at weblogic.j2ee.Application.addComponent(Application.java:126)
> > > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
> > > > arget.java:283)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
> > > > arget.java:109)
> > > > at java.lang.reflect.Method.invoke(Native Method)
> > > > at
> > > >
> >
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> > > > .java:562)
> > > > at
> > > >
> >
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
> > > > 48)
> > > > at
> > > >
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > > > nImpl.java:285)
> > > > at
> > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
> > > > at
> > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
> > > > at
> > > >
> >
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(Confi
> > > > gurationMBeanImpl.java:409)
> > > > at
> > > >
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > > > nImpl.java:287)
> > > > at
> > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
> > > > at
> > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
> > > > at
> > > >
> >
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
> > > > .java:866)
> > > > at
> > > >
> >
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
> > > > .java:853)
> > > > at
> > > >
> >
weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:838)
> > > > at
> > > >
> >
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> > > > .java:566)
> > > > at
> > > >
> >
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
> > > > 48)
> > > > at
> > > >
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > > > nImpl.java:285)
> > > > at
> > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
> > > > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1
> > 523)
> > > > at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
> > > > at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
> > > > at $Proxy8.addTarget(Unknown Source)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
> > > > anager.java:486)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
> > > > ionManager.java:557)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
> > > > ionManager.java:504)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
> > > > .java:428)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
> > > > .java:380)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
> > > > er.java:152)
> > > > at
> > > >
> >
weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(A
> > > > pplicationManager.java:643)
> > > > ####<2001-03-28 18:15:15 GMT+02:00> <Error> <J2EE> <clikra003>
> > <myserver>
> > > > <Application Manager Thread> <> <> <160001> <Error deploying
application
> > > > HashtableSessionBean: Could not deploy: 'HashtableSessionBean.jar'
> > > > Possible reasons include:
> > > > 1. The bean or an interface class has been modified but
> > > > the deployment descriptor has not been updated
> > > > 2. The database mappings in the deployment descriptor do not
> > > > match the database definition
> > > > 3. The jar file is not a valid jar file
> > > > 4. The jar file does not contain a valid bean>
> > > >
> > > > Robert
> > >
> > > --
> > > Cheers
> > >
> > > - Prasad
> > >
> > >
>
> --
> Cheers
>
> - Prasad
>
>
Similar Messages
-
Deploy Error when using Stateful Session Bean inside Webdynpro
Hi,
I'm trying to create a webdynpro project that uses a stateful session bean
I have created DC's for a EJB Module project, Enterprise Application and Webdynpro component. Created the bean, built it, added it's package to the public part, added the EJB Module to the EAR project. Built the EAR project. Added the EJB Module project and Enterprise Application project as a used DC in the Webdynpro DC.
In the Webdynpro DC I added com.sap.archive-packaging.default.update-descriptors=true in the build.properties file of the cfg directory. (using the navigator view) That resolved an error while building it.
Deployed the Enterprise Application DC without problems.
Tried to deploy the Webdynpro DC but I get the following error:
Jun 16, 2008 9:40:46 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] WARNING:
[012]Deployment finished with warning
Settings
SDM host : 10.64.36.74
SDM port : 50018
URL to deploy : file:/C:/DOCUME~1/JESCHA~1/LOCALS~1/Temp/temp59822company.nl~projempactcmp.ear
Result
=> deployed with warning : file:/C:/DOCUME~1/JESCHA~1/LOCALS~1/Temp/temp59822company.nl~projempactcmp.ear
Finished with warnings: development component 'projempactcmp'/'company.nl'/'local'/'20080616094022':Caught exception during application startup from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while starting application company.nl/projempactcmp and wait. Reason: Clusterwide execption: server ID 6060950:<--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed implicit start for company.nl/projempejb : Unknown state(5) (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : Got problems during deployment
Does anyone know what this error means and how to resolve it. I searched the forum but only found errors that look like this relating to XI not to Webdynpro.......
Thansk,
Jeschael
Edited by: J.V. Lebbink on Jun 17, 2008 6:52 AMDefault is 30mts.
This is done as a parameter in orion-ejb-jar.xml. Please look at the EJB Guide at http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/a97677/dtdxml.htm#634197 for details
regards
Debu -
Enable to Deploy Stateful session Bean
Hello EveryBody,
I have problem to deploy the stateful session bean.i have attached the error shown in server screen.Please give me the suggestion.when ever i create .ear file and paste in application directory it shows following errors.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
Module: Cart.war Error: [HTTP:101179][HTTP] Error occurred while
parsing descriptor in Web application "C:\bea\user_projects\domains\mydomain\.\m
yserver\stage\_appsdir_Cart_ear\Cart.war" [Path="C:\bea\user_projects\domains\my
domain\applications\Cart.ear", URI="Cart.war"
weblogic.xml.dom.DOMProcessingException: Neither principal-names nor externall
-defined element specified for security-role-assignment
weblogic.xml.dom.DOMProcessingException: Neither principal-names nor externall
-defined element specified for security-role-assignment
at weblogic.servlet.internal.dd.SecurityRoleAssignment.<init>(Lweblogic
servlet.internal.dd.WebAppDescriptor;Lorg.w3c.dom.Element;)V(SecurityRoleAssign
ent.java:73)
at weblogic.servlet.internal.dd.WLWebAppDescriptor.<init>(Lweblogic.ser
let.internal.dd.WebAppDescriptor;Lorg.w3c.dom.Element;)V(WLWebAppDescriptor.jav
:147)
at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebLogicXml(
org.xml.sax.InputSource;Ljava.lang.String;)V(DescriptorLoader.java:742)
at weblogic.servlet.internal.dd.DescriptorLoader.<init>(Ljava.util.jar.
arFile;Ljava.io.File;Ljava.lang.String;)V(DescriptorLoader.java:303)
at weblogic.servlet.internal.dd.DescriptorLoader.<init>(Ljava.util.jar.
arFile;Ljava.lang.String;)V(DescriptorLoader.java:235)
at weblogic.servlet.internal.WebAppModule.loadDescriptor()Lweblogic.man
Thanks in Advance.
RiazThank u for user suggestion.but can u specifiy the which type of error is this.I am using Weblogic Builder for generating xml file.
in the j2ee reference-->EJBRefs-->ADD
RefName:--ejb/Cart
JNDI Name:CartBean
EJBTYPE:session
REMOTE INTERFACE:statedemo.Cart
HomeInterface:statedemo.CartHome
I have add these parameters.but don't write anything in
link & Description field
Thanks a lot
Riaz -
Timout error when ADF Swing+BC deployed as Stateful Session Bean
i deploy the AM as stateful session bean onto OC4J 10.1.3,and the Client access them by Java Web Start.
the error message is
Exception in thread "AWT-EventQueue-0" oracle.jbo.JboException: JBO-29000: Error resuming transaction; nested exception is:
javax.transaction.InvalidTransactionException: Cannot resume transaction that has been rolledback, rollback cause=Timed out
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.processRemoteJboException(RootApplicationModuleImpl.java:435)
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.doMessage(RootApplicationModuleImpl.java:333)
at oracle.jbo.client.remote.ejb.EJBApplicationModuleImpl.doMessage(EJBApplicationModuleImpl.java:194)
at oracle.jbo.client.remote.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:6887)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1122)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1150)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest2(ApplicationModuleImpl.java:1219)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest(ApplicationModuleImpl.java:1187)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequestReceiveResponse(ApplicationModuleImpl.java:1234)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequestReceiveValues(ApplicationModuleImpl.java:1250)
at oracle.jbo.client.remote.ApplicationModuleImpl.isRangeAt(ApplicationModuleImpl.java:3856)
at oracle.jbo.client.remote.RowSetIteratorImpl.isRangeAtTop(RowSetIteratorImpl.java:1109)
at oracle.jbo.client.remote.RowSetImpl.isRangeAtTop(RowSetImpl.java:861)
at oracle.jbo.client.remote.ViewUsageImpl.isRangeAtTop(ViewUsageImpl.java:968)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.isOperationEnabled(JUCtrlActionBinding.java:409)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.isActionEnabled(JUCtrlActionBinding.java:247)
at com.kunteng.fabric.jclientview.MyJUNavigationBar._isEnabled(MyJUNavigationBar.java:1558)
at com.kunteng.fabric.jclientview.MyJUNavigationBar._updateButtonStates(MyJUNavigationBar.java:1506)
at com.kunteng.fabric.jclientview.MyJUNavigationBar$1.run(MyJUNavigationBar.java:1419)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
## Detail 0 ##
oracle.oc4j.rmi.OracleRemoteException: Error resuming transaction
at com.evermind.server.ejb.EJBTransactionManager.resumeRemote(EJBTransactionManager.java:202)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_transactionPostSuspend(StatefulSessionEJBObject.java:784)
at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
at RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.doMessage(RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.java:491)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at connection to /192.168.1.254
at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:110)
at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
at com.evermind.server.ejb.StatefulSessionRemoteInvocationHandler.invoke(StatefulSessionRemoteInvocationHandler.java:31)
at __Proxy6.doMessage(Unknown Source)
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.invokeDoMessage(RootApplicationModuleImpl.java:485)
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.doMessage(RootApplicationModuleImpl.java:325)
at oracle.jbo.client.remote.ejb.EJBApplicationModuleImpl.doMessage(EJBApplicationModuleImpl.java:194)
at oracle.jbo.client.remote.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:6887)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1122)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1150)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest2(ApplicationModuleImpl.java:1219)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest(ApplicationModuleImpl.java:1187)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequestReceiveResponse(ApplicationModuleImpl.java:1234)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequestReceiveValues(ApplicationModuleImpl.java:1250)
at oracle.jbo.client.remote.ApplicationModuleImpl.isRangeAt(ApplicationModuleImpl.java:3856)
at oracle.jbo.client.remote.RowSetIteratorImpl.isRangeAtTop(RowSetIteratorImpl.java:1109)
at oracle.jbo.client.remote.RowSetImpl.isRangeAtTop(RowSetImpl.java:861)
at oracle.jbo.client.remote.ViewUsageImpl.isRangeAtTop(ViewUsageImpl.java:968)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.isOperationEnabled(JUCtrlActionBinding.java:409)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.isActionEnabled(JUCtrlActionBinding.java:247)
at com.kunteng.fabric.jclientview.MyJUNavigationBar._isEnabled(MyJUNavigationBar.java:1558)
at com.kunteng.fabric.jclientview.MyJUNavigationBar._updateButtonStates(MyJUNavigationBar.java:1506)
at com.kunteng.fabric.jclientview.MyJUNavigationBar$1.run(MyJUNavigationBar.java:1419)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Nested exception is:
javax.transaction.InvalidTransactionException: Cannot resume transaction that has been rolledback, rollback cause=Timed out
at com.evermind.server.ApplicationServerTransaction.resume(ApplicationServerTransaction.java:330)
at com.evermind.server.ApplicationServerTransactionManager.resume(ApplicationServerTransactionManager.java:494)
at com.evermind.server.ApplicationServer$2.resume(ApplicationServer.java:4559)
at com.evermind.server.ejb.EJBTransactionManager.resume(EJBTransactionManager.java:209)
at com.evermind.server.ejb.EJBTransactionManager.resumeRemote(EJBTransactionManager.java:200)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_transactionPostSuspend(StatefulSessionEJBObject.java:784)
at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
at RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.doMessage(RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.java:491)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at connection to /192.168.1.254
at oracle.oc4j.rmi.OracleRemoteException.receive(OracleRemoteException.java:123)
at oracle.oc4j.rmi.RmiTransport.annotateException(RmiTransport.java:141)
at com.evermind.server.rmi.RMIClientConnection.handleMethodInvocationResponse(RMIClientConnection.java:812)
at com.evermind.server.rmi.RMIClientConnection.handleOrmiCommandResponse(RMIClientConnection.java:242)
at com.evermind.server.rmi.RMIClientConnection.dispatchResponse(RMIClientConnection.java:197)
at com.evermind.server.rmi.RMIClientConnection.processReceivedCommand(RMIClientConnection.java:179)
at com.evermind.server.rmi.RMIConnection.handleCommand(RMIConnection.java:154)
at com.evermind.server.rmi.RMIConnection.listenForOrmiCommands(RMIConnection.java:126)
at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:105)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Unknown Source)when i use BC4J Test tool to connect to the Stateful Session Bean ,meet the same error .The full error message is
oracle.jbo.JboException: JBO-29000: Error resuming transaction; nested exception is:
javax.transaction.InvalidTransactionException: Cannot resume transaction that has been rolledback, rollback cause=Timed out
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.processRemoteJboException(RootApplicationModuleImpl.java:435)
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.doMessage(RootApplicationModuleImpl.java:333)
at oracle.jbo.client.remote.ejb.EJBApplicationModuleImpl.doMessage(EJBApplicationModuleImpl.java:194)
at oracle.jbo.client.remote.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:6887)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1122)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1150)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest2(ApplicationModuleImpl.java:1219)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest(ApplicationModuleImpl.java:1187)
at oracle.jbo.client.remote.ApplicationModuleImpl.createAndInitRow(ApplicationModuleImpl.java:3989)
at oracle.jbo.client.remote.RowSetIteratorImpl.createAndInitRow(RowSetIteratorImpl.java:1602)
at oracle.jbo.client.remote.RowSetIteratorImpl.createRow(RowSetIteratorImpl.java:1553)
at oracle.jbo.client.remote.RowSetImpl.createRow(RowSetImpl.java:1022)
at oracle.jbo.client.remote.ViewUsageImpl.createRow(ViewUsageImpl.java:1168)
at oracle.jbo.jbotester.NavBar$rsInsert.doAction(NavBar.java:151)
at oracle.jbo.jbotester.AbstractJboAction.actionPerformed(AbstractJboAction.java:81)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
at java.awt.Component.processMouseEvent(Component.java:5488)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
at java.awt.Component.processEvent(Component.java:5253)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3955)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1774)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
## Detail 0 ##
oracle.oc4j.rmi.OracleRemoteException: Error resuming transaction
at com.evermind.server.ejb.EJBTransactionManager.resumeRemote(EJBTransactionManager.java:202)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_transactionPostSuspend(StatefulSessionEJBObject.java:784)
at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
at RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.doMessage(RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.java:491)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at connection to FUWUQI/192.168.1.254
at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:110)
at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
at com.evermind.server.ejb.StatefulSessionRemoteInvocationHandler.invoke(StatefulSessionRemoteInvocationHandler.java:31)
at __Proxy2.doMessage(Unknown Source)
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.invokeDoMessage(RootApplicationModuleImpl.java:485)
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.doMessage(RootApplicationModuleImpl.java:325)
at oracle.jbo.client.remote.ejb.EJBApplicationModuleImpl.doMessage(EJBApplicationModuleImpl.java:194)
at oracle.jbo.client.remote.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:6887)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1122)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1150)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest2(ApplicationModuleImpl.java:1219)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest(ApplicationModuleImpl.java:1187)
at oracle.jbo.client.remote.ApplicationModuleImpl.createAndInitRow(ApplicationModuleImpl.java:3989)
at oracle.jbo.client.remote.RowSetIteratorImpl.createAndInitRow(RowSetIteratorImpl.java:1602)
at oracle.jbo.client.remote.RowSetIteratorImpl.createRow(RowSetIteratorImpl.java:1553)
at oracle.jbo.client.remote.RowSetImpl.createRow(RowSetImpl.java:1022)
at oracle.jbo.client.remote.ViewUsageImpl.createRow(ViewUsageImpl.java:1168)
at oracle.jbo.jbotester.NavBar$rsInsert.doAction(NavBar.java:151)
at oracle.jbo.jbotester.AbstractJboAction.actionPerformed(AbstractJboAction.java:81)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
at java.awt.Component.processMouseEvent(Component.java:5488)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
at java.awt.Component.processEvent(Component.java:5253)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3955)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1774)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Nested exception is:
javax.transaction.InvalidTransactionException: Cannot resume transaction that has been rolledback, rollback cause=Timed out
at com.evermind.server.ApplicationServerTransaction.resume(ApplicationServerTransaction.java:330)
at com.evermind.server.ApplicationServerTransactionManager.resume(ApplicationServerTransactionManager.java:494)
at com.evermind.server.ApplicationServer$2.resume(ApplicationServer.java:4559)
at com.evermind.server.ejb.EJBTransactionManager.resume(EJBTransactionManager.java:209)
at com.evermind.server.ejb.EJBTransactionManager.resumeRemote(EJBTransactionManager.java:200)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_transactionPostSuspend(StatefulSessionEJBObject.java:784)
at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
at RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.doMessage(RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.java:491)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at connection to FUWUQI/192.168.1.254
at oracle.oc4j.rmi.OracleRemoteException.receive(OracleRemoteException.java:123)
at oracle.oc4j.rmi.RmiTransport.annotateException(RmiTransport.java:141)
at com.evermind.server.rmi.RMIClientConnection.handleMethodInvocationResponse(RMIClientConnection.java:812)
at com.evermind.server.rmi.RMIClientConnection.handleOrmiCommandResponse(RMIClientConnection.java:242)
at com.evermind.server.rmi.RMIClientConnection.dispatchResponse(RMIClientConnection.java:197)
at com.evermind.server.rmi.RMIClientConnection.processReceivedCommand(RMIClientConnection.java:179)
at com.evermind.server.rmi.RMIConnection.handleCommand(RMIConnection.java:154)
at com.evermind.server.rmi.RMIConnection.listenForOrmiCommands(RMIConnection.java:126)
at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:105)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
----- LEVEL 1: DETAIL 0 -----
oracle.oc4j.rmi.OracleRemoteException: Error resuming transaction
at com.evermind.server.ejb.EJBTransactionManager.resumeRemote(EJBTransactionManager.java:202)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_transactionPostSuspend(StatefulSessionEJBObject.java:784)
at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
at RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.doMessage(RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.java:491)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at connection to FUWUQI/192.168.1.254
at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:110)
at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
at com.evermind.server.ejb.StatefulSessionRemoteInvocationHandler.invoke(StatefulSessionRemoteInvocationHandler.java:31)
at __Proxy2.doMessage(Unknown Source)
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.invokeDoMessage(RootApplicationModuleImpl.java:485)
at oracle.jbo.client.remote.ejb.RootApplicationModuleImpl.doMessage(RootApplicationModuleImpl.java:325)
at oracle.jbo.client.remote.ejb.EJBApplicationModuleImpl.doMessage(EJBApplicationModuleImpl.java:194)
at oracle.jbo.client.remote.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:6887)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1122)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendServiceMessage(ApplicationModuleImpl.java:1150)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest2(ApplicationModuleImpl.java:1219)
at oracle.jbo.client.remote.ApplicationModuleImpl.sendRequest(ApplicationModuleImpl.java:1187)
at oracle.jbo.client.remote.ApplicationModuleImpl.createAndInitRow(ApplicationModuleImpl.java:3989)
at oracle.jbo.client.remote.RowSetIteratorImpl.createAndInitRow(RowSetIteratorImpl.java:1602)
at oracle.jbo.client.remote.RowSetIteratorImpl.createRow(RowSetIteratorImpl.java:1553)
at oracle.jbo.client.remote.RowSetImpl.createRow(RowSetImpl.java:1022)
at oracle.jbo.client.remote.ViewUsageImpl.createRow(ViewUsageImpl.java:1168)
at oracle.jbo.jbotester.NavBar$rsInsert.doAction(NavBar.java:151)
at oracle.jbo.jbotester.AbstractJboAction.actionPerformed(AbstractJboAction.java:81)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
at java.awt.Component.processMouseEvent(Component.java:5488)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
at java.awt.Component.processEvent(Component.java:5253)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3955)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1774)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Nested exception is:
javax.transaction.InvalidTransactionException: Cannot resume transaction that has been rolledback, rollback cause=Timed out
at com.evermind.server.ApplicationServerTransaction.resume(ApplicationServerTransaction.java:330)
at com.evermind.server.ApplicationServerTransactionManager.resume(ApplicationServerTransactionManager.java:494)
at com.evermind.server.ApplicationServer$2.resume(ApplicationServer.java:4559)
at com.evermind.server.ejb.EJBTransactionManager.resume(EJBTransactionManager.java:209)
at com.evermind.server.ejb.EJBTransactionManager.resumeRemote(EJBTransactionManager.java:200)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_transactionPostSuspend(StatefulSessionEJBObject.java:784)
at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
at com.evermind.server.ejb.StatefulSessionEJBObject.OC4J_invokeMethod(StatefulSessionEJBObject.java:840)
at RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.doMessage(RemoteBaseManageAppModule_StatefulSessionBeanWrapper4.java:491)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at connection to FUWUQI/192.168.1.254
at oracle.oc4j.rmi.OracleRemoteException.receive(OracleRemoteException.java:123)
at oracle.oc4j.rmi.RmiTransport.annotateException(RmiTransport.java:141)
at com.evermind.server.rmi.RMIClientConnection.handleMethodInvocationResponse(RMIClientConnection.java:812)
at com.evermind.server.rmi.RMIClientConnection.handleOrmiCommandResponse(RMIClientConnection.java:242)
at com.evermind.server.rmi.RMIClientConnection.dispatchResponse(RMIClientConnection.java:197)
at com.evermind.server.rmi.RMIClientConnection.processReceivedCommand(RMIClientConnection.java:179)
at com.evermind.server.rmi.RMIConnection.handleCommand(RMIConnection.java:154)
at com.evermind.server.rmi.RMIConnection.listenForOrmiCommands(RMIConnection.java:126)
at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:105)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595) -
Stateful session bean hot deployment error?
Hi,
i'm getting an exception ...
1. Deploy a stateful session bean.
2. Hit the server and create an instance, then remove it.
3. Change Stateful session bean source compile and hot deploy it.
4. Hit the server and try creating an instance...exception !!!!
"IllegalArgumentException: Object is not an instance of declaring class"
Please help!!!
NaveenHi Navin,
Firstly could you let me know , what option did you set in Jdeveloper to perform hot deploy ??
I would like to hot deploy Stateless Session beans on Embedded OC4J using JDeveloper.
Bhavesh -
Accessing the same stateful session bean from multiple clients in a clustered environment
I am trying to access the same stateful session bean from multiple
clients. I also want this bean to have failover support so we want to
deploy it in a cluster. The following description is how we have tried
to solve this problem, but it does not seem to be working. Any
insight would be greatly appreciated!
I have set up a cluster of three servers. I deployed a stateful
session bean with in memory replication across the cluster. A client
obtains a reference to an instance of one of these beans to handle a
request. Subsequent requests will have to use the same bean and could
come from various clients. So after using the bean the first client
stores the handle to the bean (actually the replica aware stub) to be
used by other clients to be able to obtain the bean. When another
client retrieves the handle gets the replica aware stub and makes a
call to the bean the request seems to unpredictably go to any of the
three servers rather than the primary server hosting that bean. If the
call goes to the primary server everything seems to work fine the
session data is available and it gets backed up on the secondary
server. If it happens to go to the secondary server a bean that has
the correct session data services the request but gives the error
<Failed to update the secondary copy of a stateful session bean from
home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
to the primary server will not reflect changes made on the secondary
and vice versa. If the request happens to go to the third server that
is not hosting an instance of that bean then the client receives an
error that the bean was not available. From my understanding I thought
the replica aware stub would know which server is the primary host for
that bean and send the request there.
Thanks in advance,
Justin
If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
do you?
Except of course if you switch ejb containers. Oh well.
Mike
"FBenvadi" <[email protected]> wrote:
>I've got the same problem.
>I understand from you that concurrent access to a stateful session bean
>is
>not allowed but there is a
>token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
>that
>does exactly what I need.
>What you mean 'you'll get a surprise when you go to production' ?
>I need to understand becouse I can still change the design.
>Thanks Francesco
>[email protected]
>
>"Mike Reiche" <[email protected]> wrote in message
>news:[email protected]...
>>
>> Get the fix immediately from BEA and test it. It would be a shame to
>wait
>until
>> December only to get a fix - that doesn't work.
>>
>> As for stateful session bean use - just remember that concurrent access
>to
>a stateful
>> session bean is not allowed. Things will work fine until you go to
>production
>> and encounter some real load - then you will get a surprise.
>>
>> Mike
>>
>> [email protected] (Justin Meyer) wrote:
>> >I just heard back from WebLogic Tech Support and they have confirmed
>> >that this is a bug. Here is their reply:
>> >
>> >There is some problem in failover of stateful session beans when its
>> >run from a java client.However, it is fixed now.
>> >
>> >The fix will be in SP2 which will be out by december.
>> >
>> >
>> >Mike,
>> >Thanks for your reply. I do infact believe we are correctly using
>a
>> >stateful session bean however it may have been misleading from my
>> >description of the problem. We are not accessing the bean
>> >concurrently from 2 different clients. The second client will only
>> >come into play if the first client fails. In this case we want to
>be
>> >able to reacquire the handle to our stateful session bean and call
>it
>> >from the secondary client.
>> >
>> >
>> >Justin
>> >
>> >"Mike Reiche" <[email protected]> wrote in message
>news:<[email protected]>...
>> >> You should be using an entity bean, not a stateful session bean
>for
>> >this application.
>> >>
>> >> A stateful session bean is intended to be keep state (stateful)
>for
>> >the duration
>> >> of a client's session (session).
>> >>
>> >> It is not meant to be shared by different clients - in fact, if
>you
>> >attempt to
>> >> access the same stateful session bean concurrently - it will throw
>> >an exception.
>> >>
>> >> We did your little trick (storing/retrieving handle) with a stateful
>> >session bean
>> >> on WLS 5.1 - and it did work properly - not as you describe. Our
>sfsb's
>> >were not
>> >> replicated as yours are.
>> >>
>> >> Mike
>> >>
>> >> [email protected] (Justin Meyer) wrote:
>> >> >I am trying to access the same stateful session bean from multiple
>> >> >clients. I also want this bean to have failover support so we want
>> >to
>> >> >deploy it in a cluster. The following description is how we have
>tried
>> >> >to solve this problem, but it does not seem to be working. Any
>> >> >insight would be greatly appreciated!
>> >> >
>> >> >I have set up a cluster of three servers. I deployed a stateful
>> >> >session bean with in memory replication across the cluster. A client
>> >> >obtains a reference to an instance of one of these beans to handle
>> >a
>> >> >request. Subsequent requests will have to use the same bean and
>could
>> >> >come from various clients. So after using the bean the first client
>> >> >stores the handle to the bean (actually the replica aware stub)
>to
>> >be
>> >> >used by other clients to be able to obtain the bean. When another
>> >> >client retrieves the handle gets the replica aware stub and makes
>> >a
>> >> >call to the bean the request seems to unpredictably go to any of
>the
>> >> >three servers rather than the primary server hosting that bean.
>If
>> >the
>> >> >call goes to the primary server everything seems to work fine the
>> >> >session data is available and it gets backed up on the secondary
>> >> >server. If it happens to go to the secondary server a bean that
>has
>> >> >the correct session data services the request but gives the error
>> >> ><Failed to update the secondary copy of a stateful session bean
>from
>> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
>> >> >to the primary server will not reflect changes made on the secondary
>> >> >and vice versa. If the request happens to go to the third server
>that
>> >> >is not hosting an instance of that bean then the client receives
>an
>> >> >error that the bean was not available. From my understanding I
>thought
>> >> >the replica aware stub would know which server is the primary host
>> >for
>> >> >that bean and send the request there.
>> >> >
>> >> >Thanks in advance,
>> >> >Justin
>>
>
>
-
Stateful session Bean in Model not working
I made a sample application very very simple, and the weblogic server cant find the @stateful annotation on the class. is it there another possibility? here i post the error i get:
[Running application MyTest1 on Server Instance IntegratedWebLogicServer...]
[09:48:51 PM] ---- Deployment started. ----
[09:48:51 PM] Target platform is (Weblogic 10.3).
[09:48:52 PM] Retrieving existing application information
[09:48:52 PM] Running dependency analysis...
[09:48:52 PM] Deploying 3 profiles...
[09:48:53 PM] Wrote Web Application Module to /home/issanllo/.jdeveloper/system11.1.1.2.36.55.36/o.j2ee/drs/MyTest1/ViewWebApp.war
[09:48:53 PM] Wrote EJB Module to /home/issanllo/.jdeveloper/system11.1.1.2.36.55.36/o.j2ee/drs/MyTest1/ModelEJB.jar
[09:48:53 PM] Wrote Enterprise Application Module to /home/issanllo/.jdeveloper/system11.1.1.2.36.55.36/o.j2ee/drs/MyTest1
[09:48:53 PM] Deploying Application...
<03-jun-2010 21H48' CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1275594533727' for task '2'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(ModelEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation..'
weblogic.application.ModuleException: Exception preparing module: EJBModule(ModelEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation..
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:219)
at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1210)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
Truncated. see log file for complete stacktrace
>
<03-jun-2010 21H48' CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'MyTest1'.>
<03-jun-2010 21H48' CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(ModelEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation..
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:219)
at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1210)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
Truncated. see log file for complete stacktrace
>
#### Cannot run application MyTest1 due to error deploying to IntegratedWebLogicServer.
[09:48:54 PM] #### Deployment incomplete. ####
[09:48:54 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
[Application MyTest1 stopped and undeployed from Server Instance IntegratedWebLogicServer]
and the very simple class with a Local and Remote interfaces at Model project in jDeveloper 11g (11.1.1.3)
package test.core;
import java.util.ArrayList;
import java.util.List;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateful;
@Stateful(name = "ControlSessionBean", mappedName = "MyTest1-Model-ControlSessionBean")
public class ControlSessionBean implements ControlSessionRemote,
ControlSessionLocal
private String username;
private String password;
public ControlSessionBean()
public List simple()
List <String> s = new ArrayList();
s.add(username);
s.add(password);
return s;
any suggestions why it is not working??
sincerely
Israel S Llorensnot working... i tried to make the stateful session bean Control.. and is still not working the error i get now is this one:
<04-jun-2010 16H29' CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1275661769594' for task '9'. Error is: 'weblogic.application.ModuleException: Could not setup environment'
weblogic.application.ModuleException: Could not setup environment
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1499)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:442)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
Truncated. see log file for complete stacktrace
Caused By: weblogic.deployment.EnvironmentException: [J2EE:160200]Error resolving ejb-ref 'gecu.view.LoginBean/controlBean' from module 'GeCU_Web_view_root' of application 'GeCU_Web'. The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because no EJBs in the application were found to implement the 'gecu.model.ControlSession' interface. Please link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.
at weblogic.deployment.BaseEnvironmentBuilder.autowireEJBRef(BaseEnvironmentBuilder.java:427)
at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:502)
at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3117)
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1497)
Truncated. see log file for complete stacktrace
>
<04-jun-2010 16H29' CEST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 9 task for the application 'GeCU_Web'.>
<04-jun-2010 16H29' CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'GeCU_Web'.>
<04-jun-2010 16H29' CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Could not setup environment
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1499)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:442)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
Truncated. see log file for complete stacktrace
Caused By: weblogic.deployment.EnvironmentException: [J2EE:160200]Error resolving ejb-ref 'gecu.view.LoginBean/controlBean' from module 'GeCU_Web_view_root' of application 'GeCU_Web'. The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because no EJBs in the application were found to implement the 'gecu.model.ControlSession' interface. Please link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.
at weblogic.deployment.BaseEnvironmentBuilder.autowireEJBRef(BaseEnvironmentBuilder.java:427)
at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:502)
at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3117)
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1497)
Truncated. see log file for complete stacktrace
>
[04:29:35 PM] #### Deployment incomplete. ####
[04:29:35 PM] Remote deployment failed -
How can I create a stateful session bean?
I created a stateless session bean. Now I want to make it be a stateful session bean. How can I do? Where can I find a session bean sample?
Thanks
QingLook at this site. The tutorial explains it all.
Well if you want to convert your stateless EJB to stateful, all you have to do is change the deployment descriptor and re-deploy the ejb. You should be ready to go.
All the best. -
Share stateful session bean in JSF managed beans with different scope
Hi,
I have a JSF application and I want to try to use of stateful session beans.
So I created a new stateful session bean and its local interface.
@Stateful
public class StatefulSessionBean implements StatefulSessionBeanLocalInterface{
private String name;
@Local
public interface StatefulSessionBeanLocalInterface {
...In my JSF application I have a mananed bean with session context which registers the new interface by
this annotation
@EJB(name="sessionbeanref", beanInterface=StatefulSessionBeanLocalInterface.class) and set the name to something.
Now I want to fetch this name in another managed bean with request scope. So I looked up the bean and tried to get the name.
StatefulSessionBeanLocalInterface = (StatefulSessionBeanLocalInterface) new InitialContext().lookup("java:comp/env/sessionbeanref");
System.out.println(currentmailingbean.getName());but the name is null.
Why?The xsd was created via the netbeans J2EE enterprise application dialog and I think its the most recent.
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">All other annotations seem to work.
Wouldnt the lookup completely fail if the deployment process thought that it is version 1.4 ? -
Web Service from stateful Session Bean deleted after server restart
Hi,
i created a stateful session bean and from this a web service.
I am able to deploy it and it works really fine.
My problem is: after a server restart the web service is gone and i
have to deploy it again.
I have some other web services (but these are web services from stateless session beans)
but they "survive" the server restart.
I don't want to deploy the web service after every server restart, did I forget something or
is it a general problem of stateful session beans or web services?
Thanks in advance
JensHello Björn,
I am not quite sure what your problem is but did you have a look at these articles:
http://help.sap.com/saphelp_nw04/helpdata/en/4d/993441c73cef23e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/be/2e2c4142aef623e10000000a155106/frameset.htm
I hope they can give you some idea.
Regads
Vyara -
1) Second thread call to stateful session bean.
Hi Friend,
I read your threads on otn and i compared your problem with us and i analysed that your application and my application is same, So Plese can you help me in some issues.
Friend, Please help me in these issues, Thanks for this
We have very big ADF Swing+BC Application and deployed as Stateful Session Bean. in my application there are 500 Application Modules,For each application module i created Stateful session beans and deployed it on OC4J Container but when working on deployed application then i am getting time out error after 15 min of working.
1). I set that parameter that you mentioned i.e jbo.ejb.txntimeout = 86400,but still it is giving me same error.
2). Second Issue is of ---ORA-01000: maximum open cursors exceeded
For this issue i chaged the Database Parameter i.e OpenCurser=2000, but still it is giving me same error,
is there any parameter on application module required to change so that this error will not come.
3). When i close the form then application module is not releasing database connection.
4). (oracle.oc4j.rmi.OracleRemoteException) Second thread call to stateful session bean
This error is also coming when I am using deployed application for long time i.e more than 15 min for Heavy TransactionsHi Suyog,
How r u?
We all are fine.
I alerady tried for the Max Curser Property but it is not helpfull.
I think again i have to go for closing opened db RS and statements.
Thanks
Vijay -
Problem using application client for local stateful session bean
Hi,
I have deployed a local stateful session bean in Sun J2EE 1.4 application server.
On running the applclient for the stateful session bean application client i get the following error:
Warning: ACC006: No application client descriptor defined for: [null]
cant we use application client for local stateful session beans. becoz the application runs smoothly when i changed the stateful sesion bean to remote.Hi,
No, an ejb that exposes a local view can only be accessed by an ejb or web component packaged within the same application. Parameters and return values for invocations through the ejb local view are passed by reference instead of by value. That can't work for an application client since it's running in a separate JVM.
--ken -
When will Stateful Session Bean be removed?
I develop a stateful session bean and deploy it in the oc4j server successfully.
I write a java GUI Frame.
This Frame call this stateful Session bean and get some data,
and hold its remote interface reference as Frame's private member.
Code like that:
public class CargoFrame extends JFrame
//private member
private DataPager dataPager;
I found that before i release CargoFrame, Stateful session bean will be removed.
And System report session time out.
And i want to know when stateful session bean will be removed,
and how to set the session time?Default is 30mts.
This is done as a parameter in orion-ejb-jar.xml. Please look at the EJB Guide at http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/a97677/dtdxml.htm#634197 for details
regards
Debu -
Plz help!! idempotent methods stateful session beans? (failover)
plz help!! idempotent methods stateful session beans? (failover)
Hi there,
Im trying to failover my shopping cart implemented using stateful ejb, the replication
is working but the failover is not (Object not found exception....).
By design is hard to think on an stateful ejb using idempotent methods, but after
checking the documentation in detail im completely confused, so im starting to
wonder if i should use idempotent methods or manual retry in case one server is
down.
Plz take a loo at these explanations about faiolver in the WLS edocs.
"....With clustered objects, automatic failover generally occurs only in cases
where the object is idempotent.....Because of this, replica-aware stubs will not,
by default, attempt to retry a method that fails after the request is sent but
before it returns. This behavior can be overridden by marking a service idempotent..."
BUT
"By default, a stateful session bean's Home stub provides load balancing and failover
for its method invocations to any clustered server where the bean is deployed...."
So is possible to achieve automatic failover (not only load balancing) for stateful
ejb without having to worry about state-changes or manual retry. (i know the retry
is requiered if the server crashed just before finishing a transaction but this
is not what im talking about).
Any help will be highly appreciated
Alan
Ryan,
Yes, im deploying using In-memory replication and clusterable elements, when try
to invoke the method (after one of the nodes is down) i recieve an "java.rmi.NoSuchObjectException:
Bean has been deleted".
I believe all this could be related to some sort of issue with JNDI Lookup in
the cluster, but haavent been able to get a clue to make it work....(almost desesperate
by now)
Alan
"ryan upton" <[email protected]> wrote:
>Alan,
>
>If the state isn't maintained during failover I would suspect a
>configuration error. Have you set the <replication-type> element within
><stateful-session-clustering> tag in the bean's deployment descriptor?
>
>"Alan" <[email protected]> wrote in message
>news:40e17cf7$1@mktnews1...
>>
>> Ryan,
>>
>>
>> Maybe i didnt explain myself, in the scenario im dealing with I KNOW
>the
>method
>> finished succesfully (example, the user succesfully added an item to
>a
>cart).
>>
>>
>> Just after that one of the nodes goes down, and the user decides to
>add a
>new
>> item (new invocation , not a retry of failed one) on the same session.
>>
>> This is the case in which failover should work automatically as you
>say,
>meaning
>> the new method invokation should be able to retrieve the session state
>info from
>> the replica and switch the primary.....Well, this is the part wich
>isnt
>working
>> :( as i understand it should transparently
>>
>> I believe could be a config issue , but have no way to make it work.
>>
>> Regards,
>>
>> Alan
>> "ryan upton" <[email protected]> wrote:
>> >
>> >"Alan" <[email protected]> wrote in message
>news:40e06296@mktnews1...
>> >>
>> >> Ryan,
>> >>
>> >> Thanks for clearing the both conditions a bit more, in this case
>my
>> >issue
>> >has
>> >> to do with the scenario #1 in which subsequent calls (invocations)
>> >go to a
>> >node
>> >> which isnt avaliable(down), do you have any idea of in what conditions
>> >the
>> >"automnatic"
>> >> failover would fail??? (meaning why the stub would try to dispatch
>> >a call
>> >to the
>> >> same previous node)
>> >>
>> >> Thanks for the help again
>> >>
>> >
>> >Subsequent calls won't go to a node that's down. That's the whole
>> >point
>> >;-). Failover is always automatic, what you are getting confused
>on
>> >is
>> >automatic method re-execution upon failover which happens if the method
>> >has
>> >been marked as idempotent. The logic is this: if I failover to an
>EJB
>> >that
>> >I know is still alive, I can't safely call the same method again.
> Why?
>> >Because I don't know how much of the method completed the last time
>before
>> >the previous bean's failure. So if the bean can yield multiple results
>> >from
>> >multiple invocations I had better play it safe and not re-execute
>the
>> >method
>> >on the bean I failed over to (unless it's idempotent because in that
>> >case it
>> >doesn't matter how many times I call it, it always does the same thing).
>> > In
>> >scenario #1 and #2 failover is automatic and all new calls are executed
>> >against the bean the client failed over to, but only idempotent methods
>> >are
>> >re-executed.
>> >
>> >
>>
>
>
-
Error While passivating Stateful session bean
I also have same problem when WL passivating. However, the exception throwing from
WL saying the "Ignoring exception raised while passivating".
My question is will that exception lead to failure of passivating and evenually
lead to memory leakage? I just thought that the memory is still in cache either
removed or passivated, as a result more and more memory will be used up as more
failure occurs.
Frank
Rob Woollen <[email protected]> wrote:
It looks like you have a reference to a DB Connection as a member
variable. This reference should be transient. You can re-acquire it
in
ejbActivate.
-- Rob
Hemant Arora wrote:
Hi
Can anybody please clarify the error that I'm getting while runningthe
stateful session bean with weblogic
I have instantiated 20 stateful session beans all using the DB connection
but if the connection is unaailable I'm making the beans to wait.
I'm not removeing the beans and again making the instance of 20 another
beans
The max beans in cache is 25.
Thanks
Hemant
This is the output at the console of the weblogic
ejbPassivate()
Tue Jul 17 20:58:00 GMT+05:30 2001:<I> <EJB JAR deployment
d:/weblogic/myserver/romanCount.jar> Ignoring exception raised while
passivating:
java.io.NotSerializableException:
weblogic.jdbc20.rmi.internal.ConnectionImpl
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com
Maybe you are looking for
-
How can I use my iPod as source for reinstalled iTunes?
Hello @ all. Unfortunately I had to completely reinstall my system (WinXP Pro PC) and lost my media library! How can I use my iPod as a source to copy all my songs and settings (incl. covers, aso) to iTunes? iPod: 30GBs Video iPod iTunes Version: 7.0
-
I have a Mac book pro(13 inch non-retina, i7) with regular drive, I want to replace the drive with SSD, so can I do it for Mac book pro purchased in 2012 and which SSD is recommended. I am looking for 500 to 700GB SSD. Thanks
-
Delete single call/sms in log for Nokia E 51 & E ...
Hi, Can someone advice me how can I delete single entry (call or sms) in log? I have Nokia E 51 and E 66 and it can be done, deleinge but all comunications. Doe anyone know how to do that, is there any short cut or it can be done by installing some s
-
Guys please i need help urgently with face time!!
Please help me... so me and my girlfriend sleep togethernat the phone.. When she is a sleep of course there is no noise but there is alway that " interference" noise.. But now when i block my phone this noise disappear it seems like it is muted
-
I have cs4 bridge and cs5 bidge installed on the same windows 7 box. Every time I launch cs5 bridge cs4 bridge comes up instead.