Creating a session bean automatically on deployment
Hi,
I want to create a session bean automatically on deployment of my application to the container. Is this possible?
Thanks!
Create a servlet as a Ejb client & specify the client servlet
in the <load-on-startup> element of the web.xml deployment descriptor.
Similar Messages
-
App No Longer Works After Creating EJB Session Bean
I am using EJB3.0 and using JDEV 11g, PS1. I have used EJB to create my entities from tables and then i created my ejb diagram. After doing that my application (i have a jspx page) that runs fine. Once I create my session bean, I am no longer able to run my application. After creating my session bean I get the following error when I run the application (i.e. not at build/compile time).
<Feb 12, 2010 3:28:57 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266017332257' for task '5'. Error is: 'java.lang.ClassNotFoundException: javax.faces.webapp.ConverterELTag'
java.lang.ClassNotFoundException: javax.faces.webapp.ConverterELTag
If i delete the sessionejb.java, ejbbean.java, and the ejblocal.java files, I am able to run my application again. Am I missing something or is this a bug?
Thanks.Did you solved the problemn? I'm getting this, when I try run my App doesn't work, but if I deploy to WLS Integrated and go to URL it's work...
-
Exception creating stateless session bean
hello, can some one tell what is the cause and the solution of the folowing exception :
EJB5070 Exception creating stateless session bean : [{0}]
com.sun.enterprise.InjectionException: Exception attempting to inject Env-Prop: ejb3.INplateformFacade/timerService@Field-Injectable Resource. Class name = ejb3.INplateformFacade Field name=[email protected]@ejb3.INplateformFacade/timerService@@ into class ejb3.INplateformFacade
at com.sun.enterprise.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:387)
at com.sun.enterprise.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:206)
at com.sun.enterprise.util.InjectionManagerImpl.injectInstance(InjectionManagerImpl.java:127)
at com.sun.ejb.containers.StatelessSessionContainer.createStatelessEJB(StatelessSessionContainer.java:533)
at com.sun.ejb.containers.StatelessSessionContainer.access$100(StatelessSessionContainer.java:111)
at com.sun.ejb.containers.StatelessSessionContainer$SessionContextFactory.create(StatelessSessionContainer.java:772)
at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:199)
at com.sun.ejb.containers.StatelessSessionContainer._getContext(StatelessSessionContainer.java:486)
at com.sun.ejb.containers.BaseContainer.getContext(BaseContainer.java:1675)
at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1229)
at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:195)
at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:127)
at $Proxy63.tachePlanifier(Unknown Source)
thanx on advancei dont think so it is a typo in the name.
here is my source code :
@Stateless
public class INplateformFacade implements INplateformFacadeLocal {
@PersistenceContext
private EntityManager em;
private Date datePrevis;
@Resource
TimerService timerService;
@Timeout
public void traitementPlanifier(Timer timer) throws NamingException {
listerLeReprtoir(ChercherReprtoir());
public void tachePlanifier(Date datePrevis) {
this.datePrevis = datePrevis;
timerService.createTimer(datePrevis, null);
} -
No resource available error coming while trying to create a session bean and loading a resultset
Hi,
I'm trying to create a session bean and load a resultset within it when the following
error occurs.What could be the reason?Need an immediate response.Thanks
in advance
Thomas
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
Start server side stack tCrraecaet:i
njga vTaa.brlmeib.eRaenm oSt|eSException|:W OECJTBL _EMxScTe
ptCioonnn:e;t innegs tteod Seexrcveeprt.i opnl si sw:a i
t
jaCvraexa.teijnbg. ETJaBbElxecbeepatni oIn|
D |-W OwAiDtVhI _nDeAsTt
ed exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:279)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:279)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.sql.SQLException: weblogic.common.ResourceException: No resources available
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:279)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
Exception occurred during event dispatching:
java.lang.NullPointerException
at BaseClasses.busWORRUR01.<init>(busWORRUR01.java:261)
at BaseClasses.frmWorrur01.butStartActionPerformed(frmWorrur01.java:186)
at BaseClasses.frmWorrur01.access$1(frmWorrur01.java:175)
at BaseClasses.frmWorrur01$2.actionPerformed(frmWorrur01.java:123)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1450)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1504)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:378)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:250)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:216)
at java.awt.Component.processMouseEvent(Component.java:3715)
at java.awt.Component.processEvent(Component.java:3544)
at java.awt.Container.processEvent(Container.java:1164)
at java.awt.Component.dispatchEventImpl(Component.java:2593)
at java.awt.Container.dispatchEventImpl(Container.java:1213)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2451)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:2216)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2125)
at java.awt.Container.dispatchEventImpl(Container.java:1200)
at java.awt.Window.dispatchEventImpl(Window.java:926)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:339)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)Thomas wrote:
Hi,
I'm trying to create a session bean and load a resultset within it when the following
error occurs.What could be the reason?Need an immediate response.Thanks
in advance
ThomasIt means the pool doesn't have a connection available for this thread to use, after waiting
some time for any other thread to return one. Either your pool is not big enough, or your
bean code may sometimes be forgetting to close any connection it gets. Note that in
a stateful session bean, you may fall into the trap of retaining a JDBC connection open
for the duration of the session. If you do this, your pool must have as many connections
as the maximum number of simultaenous sessions you want to support. Usually the aim is
to obtain a pool connection, use it, and return it to the pool, all within any single response
to the client. Then you only need as many pool connections as there are execute threads
in the server. Having a DBMS transaction that spans user input is an invitation to deadlocks,
bottlenecks in performance etc.
Joe Weinstein at B.E.A.
>
>
java.rmi.RemoteException: EJB Exception:; nested exception is:
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
Start server side stack tCrraecaet:i
njga vTaa.brlmeib.eRaenm oSt|eSException|:W OECJTBL _EMxScTe
ptCioonnn:e;t innegs tteod Seexrcveeprt.i opnl si sw:a i
t
jaCvraexa.teijnbg. ETJaBbElxecbeepatni oIn|
D |-W OwAiDtVhI _nDeAsTt
ed exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:279)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:279)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.sql.SQLException: weblogic.common.ResourceException: No resources available
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
--------------- nested within: ------------------
javax.ejb.EJBException:
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
javax.ejb.EJBException
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available]
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:279)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[java.sql.SQLException: weblogic.common.ResourceException: No resources available
Start server side stack trace:
java.sql.SQLException: weblogic.common.ResourceException: No resources available
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:197)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:219)
at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:82)
at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
Exception occurred during event dispatching:
java.lang.NullPointerException
at BaseClasses.busWORRUR01.<init>(busWORRUR01.java:261)
at BaseClasses.frmWorrur01.butStartActionPerformed(frmWorrur01.java:186)
at BaseClasses.frmWorrur01.access$1(frmWorrur01.java:175)
at BaseClasses.frmWorrur01$2.actionPerformed(frmWorrur01.java:123)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1450)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1504)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:378)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:250)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:216)
at java.awt.Component.processMouseEvent(Component.java:3715)
at java.awt.Component.processEvent(Component.java:3544)
at java.awt.Container.processEvent(Container.java:1164)
at java.awt.Component.dispatchEventImpl(Component.java:2593)
at java.awt.Container.dispatchEventImpl(Container.java:1213)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2451)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:2216)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2125)
at java.awt.Container.dispatchEventImpl(Container.java:1200)
at java.awt.Window.dispatchEventImpl(Window.java:926)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:339)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:85) -
How to lookup a EJB 3.0 session bean which is deployed in WebLogic 10.3
Now Jdeveloper 11.1.1, is giving WebLogic server 10.3.
With internal WebLogic server, when I created a Sample client, it generated code as:
private static Context getInitialContext() throws NamingException {
Hashtable env = new Hashtable();
// WebLogic Server 10.x connection details
env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
env.put(Context.PROVIDER_URL, "t3://127.0.0.1:7101");
return new InitialContext( env );
public static void main(String [] args) {
try {
final Context context = getInitialContext();
DefaultSession defaultSession = (DefaultSession)context.lookup("property-DefaultSession#com.vs.property.model.session.DefaultSession");
} catch (Exception ex) {
}How to update the above code to lookup the EJB 3.0 session beans with an external WebLogic server 10.3?
Is there any documentation available on how to install weblogic, troubleshoot, debug, WebLogic server 10.3?
regds
-rajuRaju,
Hi, to start, here is a tutorial on a quickstart web application using an EJB 3.0 stateless session bean that fronts a container managed EclipseLink JPA entity manager on WebLogic 10.3, you will find references there to other general WebLogic documentation.
[http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial]
using @EJB injection on the client instead of a JNDI lookup as below
[http://edocs.bea.com/wls/docs103/ejb30/annotations.html#wp1417411]
1) in your second env.put I noticed that your t3 port is 7101, I usually use the default 7001 - but It looks like this port is valid for the JDeveloper embedded version of WebLogic server runs - just verify that it matches the port of your server.
2) your name#qualified-name lookup looks ok. Verify that the jndi-name element is set in your weblogic-ejb-jar.xml for non injection clients like the following
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ApplicationService</ejb-name>
<jndi-name>ApplicationService</jndi-name>
3) as a test outside of your application - launch the WebLogic admin console and goto the testing tab of your bean in [Home > Summary of Deployments > "application" > "session bean name"
thank you
/michael : http://www.eclipselink.org -
I create simple session bean in jdeveloper and it has a problem in lookup
the code of bean
import java.util.*;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
import javax.naming.*;
public class CartClient {
public static void main(String[] args) {
try {
Context initial = getInitialContext() ;
// Object objref = initial.lookup("java:comp/env/ejb/SimpleCart");
Object objref = initial.lookup("Cart");
CartHome home =
(CartHome)PortableRemoteObject.narrow(objref,
CartHome.class);
Cart shoppingCart = home.create("Duke DeEarl","123");
shoppingCart.addBook("The Martian Chronicles");
shoppingCart.addBook("2001 A Space Odyssey");
shoppingCart.addBook("The Left Hand of Darkness");
Vector bookList = new Vector();
bookList = shoppingCart.getContents();
Enumeration enumer = bookList.elements();
while (enumer.hasMoreElements()) {
String title = (String) enumer.nextElement();
System.out.println(title);
shoppingCart.removeBook("Alice in Wonderland");
shoppingCart.remove();
System.exit(0);
} catch (BookException ex) {
System.err.println("Caught a BookException: " + ex.getMessage());
System.exit(0);
} catch (Exception ex) {
System.err.println("Caught an unexpected exception!");
ex.printStackTrace();
System.exit(1);
private static Context getInitialContext() throws NamingException {
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "admin");
env.put(Context.PROVIDER_URL, "ormi://localhost:23791CartApp");
return new InitialContext(env);
} javax.naming.NameNotFoundException: Cart not found
java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
RMIContext.java:130
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
InitialContext.java:350
void CartClient.main(java.lang.String[])
CartClient.ja
exceptionPlease post your question in jdeveloper forum at
JDeveloper and ADF
for quick response.
Regards,
Anupama
http://otn.oracle.com/sample_code/content.html -
Creating Session Bean Facade Methods Off EJB QL
Hello,
I'm trying to follow the documentation for creating a Session Bean that has facade methods for various Entity Beans. When I add a named query:
@NamedQuery(name = "Debtor.findDebtorById", query = "select o from Debtor o where o.debtorId = ?1")
I end up with the following facade method:
/** <code>select object(o) from Debtor o where o.DEBTOR_ID = ?1</code> */
public List<Debtor> queryDebtorFindDebtorById(Object p1) {
return em.createNamedQuery("Debtor.findDebtorById").setParameter(0, p1).getResultList();
I see two issues here:
1) The type of the input parameter is supposed to be a long, as the Entity Bean field looks like:
@Id
@Column(name="DEBTOR_ID", nullable = false)
private Long debtorId;
2) The parameter being set is '0' instead of '1'.
Is there a known issue with generating this code in JDev? Or am I doing something wrong?another strange problem.
i have an APplication server added ( JBOSS ).
when i create deployment profile (EAR ) application server is showed in the ComboBox .
But when i create Java Test Client for some EJB and when i check " Connect Remote Application server" there is 2 comboboxes
J2EE Application
App Server Connection.
first combo is ok there is EJB applicaiton
Secound is empty .. but i Have App Server.
Another think is that when i create EJB 3.0 its BAD to see J2EE app it must be J EE 5 app or just Java EE app -
Using only one method in session bean to create web service
Hi all,
I hhave a scenario where i am inserting and retrieving data from dict table using web service.
For this i have created a session bean and a wrapper class.
The session bean has two methods: insertRecords(), and viewRec().
so while creating a web service i need to include two methods.
I want to have only one method where i can pass a parameter as operation and if it is "I", then i can call the insert method and if it is "S" i can call view method.
I tried doing that bt i am stuck up with the return type.
Insert method has return type as array of wrapper class and
view method has wrapper class as return type ...
Is this scenario possible..??
or is there any other way to do this???
Plz let me knw..
Thankls n regards,
AnkitaHi Siddharth,
Im really sorry..
i cudnt get u ..
Actually these r methods:
public DemoDicModel[] viewRecords()
and
public DemoDicModel insertRecords(
String title,
String desc,
String status)
and im trying this:
public DemoDicModel[] getMethods(String operation,String title,String desc, String st)
DemoDicModel[] demoModel =null;
DemoDicModel model = new DemoDicModel();
if(operation == "show")
demoModel = viewRecords();
if(operation == "ins")
model = insertRecords(title,desc,st);
model.setMsg("RECORDS GENERATED");
demoModel=
return demoModel;
im stuck up with insert operation.
can u plz explain me in detail.
thanks,
ankita -
Cannot deploy a EJB 3.0 Session bean to the OAS 10.1.3.4
Hi All,
I am unable to deploy a EJB 3.0 Session bean with no deployment descriptors to OAS 10.1.3.4 App server.This Session bean is also exposed as a web service using annotations. I am able to deploy this bean to a standalone oc4j 10.1.3.x containers and test it successfully.
i have written a simple stateless session bean ( exposed as webservice) and every bean is having issues with deployment having the same exception stated below
Can some one please help as i need to deploy this urgently.
below is the session bean code:
import javax.ejb.Stateless;
@Stateless(name="SiebelQuoteEJB")
public class SiebelQuoteEJBBean implements SiebelQuoteEJBLocal,
SiebelQuoteEJBWebService {
public SiebelQuoteEJBBean() {
public String publishMessage(String message,String type) throws java.rmi.RemoteException {
client.publishMessage(message,type);
return "SUCCESS";
Below is the error while deploying:
11/01/06 15:03:49 WARNING: Application.setConfig Application: javasso is in failed state as initialization failed.
java.lang.NullPointerException
11/01/06 15:03:50 WARNING: Application.setConfig Application: SiebelQuoteEJB is in failed state as initialization failed.
java.lang.InstantiationException: Error initializing ejb-modules: null Error parsing application-server config file: null
11/01/06 15:03:50 java.lang.NullPointerException
at com.evermind.server.ObjectReferenceCleaner.cleanupApplicationLogLevels(ObjectReferenceCleaner.java:166)
at com.evermind.server.ObjectReferenceCleaner.loaderDestroyed(ObjectReferenceCleaner.java:88)
at oracle.classloader.EventDispatcher.loaderDestroyed(EventDispatcher.java:248)
at oracle.classloader.PolicyClassLoader.close(PolicyClassLoader.java:1113)
at oracle.classloader.PolicyClassLoader.close(PolicyClassLoader.java:1041)
at com.evermind.server.ApplicationStateRunning.destroyClassLoaders(ApplicationStateRunning.java:1171)
at com.evermind.server.Application.stateCleanUp(Application.java:3635)
at com.evermind.server.Application.setConfig(Application.java:506)
at com.evermind.server.Application.setConfig(Application.java:355)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1895)
at com.evermind.server.ApplicationServer.initializeDeployedApplications(ApplicationServer.java:1651)
at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1034)
at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
at java.lang.Thread.run(Thread.java:736)which jdk version? Had this with 1.6 and had to install an up-to-date jdbc.
-
Minimal requirements for remote client app to call a EJB 3 session bean
I'm just starting to get into EJBs, trying to learn the EJB 3 APIs. I kind of understand the setup on the server side to create a session bean. What I don't understand is what I would have to deploy for each of the remote client app (Swing-based GUI or something like that) installations. Of course, the client app code would have to be deployed to each client desktop, but what stuff related to the session bean? Just the session bean interface class?
For ease of discussion, let's say my bean is CalculatorBean, having two interfaces, CalculatorRemoteIface and CalculatorLocalIface. Let's also say my client app, CalculatorUI, is a simple Swing-based GUI that grabs a reference to a CalculatorBean.
Other than just the Swing-based classes and the JRE, what JARs/classes will I want to deploy to each desktop?
(Please assume the latest Sun Java System App Server 9 and Java EE 5, if you are familiar with them.)Personally- I would deploy your backend
in EJB 3.0, but then expose it as a web service. It
is MUCH easier for your clients to connect to a web
service (and mantain that code), then to have them
connect via RMI/JNDI.Oh, I would say it's quite the opposite. RMI/JNDI is MUCH easier from a client point of view than web services. To make web services work easy from the client side you have to generate code and the tools that generate code from a web services wsdl file doesn't do a great job today. But that was not the question. But take some time reading this article about webservices...it's quite funny and spot on: http://wanderingbarque.com/nonintersecting/2006/11/15/the-s-stands-for-simple
Now to your question, yes you will need the remote interface on the client side.
/klejs -
WLS10 and Stateless Session Bean
I tried to create EJB3 application example.
1. Created Stateless Session Bean that implements Remote and Local interfaces:
Session Bean code:
package com.session;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
@Stateless(mappedName="SessionBeanService")
@Remote(ISessionBeanRemote.class)
@Local(ISessionBeanLocal.class)
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class SessionBean implements ISessionBeanLocal,
ISessionBeanRemote
public String reply(){
return "MySessionBean - success !!!";
Remote Interface code :
package com.session;
public interface ISessionBeanRemote
public String reply();
Local Interface code:
package com.session;
public interface ISessionBeanLocal
public String reply();
application.xml:
<?xml version="1.0" encoding="UTF-8"?>
<application 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/application_5.xsd"
version="5">
<display-name>EJB3 Sample Application</display-name>
<module>
<ejb>beans.jar</ejb>
</module>
</application>
weblogic-application.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-application PUBLIC
"-//BEA Systems, Inc.//DTD WebLogic Application 8.1.0//EN"
"http://www.bea.com/ns/weblogic/90/weblogic-application.xsd">
<weblogic-application>
<classloader-structure>
<module-ref>
<module-uri>beans.jar</module-uri>
</module-ref>
</classloader-structure>
</weblogic-application>
2. I packaged classes into EAR file and deployed to WLS10.
I didn't include any weblogic specific XML descriptors besides weblogic-application.jar.
My client code lookes as follows:
public void test(){
Context context = getMyServerContext();
// THIS JNDI NAME I SEE ON MY SERVER JNDI TREE
String jndiName = "sessionbeansbeans_jarSessionBean_ISessionBeanRemote";
Object obj;
obj = context.lookup(jndiName);
System.out.println(" obj class : " + obj.getClass().getName());
ISessionBeanRemote remote = (ISessionBeanRemote) PortableRemoteObject.narrow(
obj, ISessionBeanRemote.class );
String res = remote.reply();
System.out.println("res : "+res);
I get an Exception:
Exception occurred!
java.lang.ClassCastException: Cannot narrow remote object to com.session.ISessionBeanRemote
at weblogic.iiop.PortableRemoteObjectDelegateImpl.narrow(PortableRemoteObjectDelegateImpl.java:242)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
at ca.cgi.mvest.test.server.wms.GlFacadeTest.runTest(GlFacadeTest.java:91)
at ca.cgi.mvest.test.server.wms.GlFacadeTest.<init>(GlFacadeTest.java:53)
at ca.cgi.mvest.test.server.wms.GlFacadeTest.main(GlFacadeTest.java:151)
java.lang.ClassCastException: Cannot narrow remote object to com.session.ISessionBeanRemote
My server console have the following output:
Root cause of ServletException.java.lang.NoClassDefFoundError: com/session/SessionBean_7pp7ls_ISessionBeanRemot
eIntf
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
4)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericCla
ssLoader.java:338)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic
ClassLoader.java:291)
Truncated. see log file for complete stacktrace
Server logs a problem already on the line when I do lookup
on JNDI name even before narrow();
It looks like my EAR was missing something. But server never complained during deployment.
May be someone can direct me to a real sample of Weblogic10-ejb3.0 application, since examples that come with WLS 10 intallation combersome and do not follow
docmentation.
Thanks in advance for any suggestion.Hello Freind
The main different b\w stateful and statless is that stateful maintain state of method conversation means it has record that which method call before this method
but in case of stateless conversation state does not saved second different we can say that create method in stateless having no parameter but statefull having parameter I think u can understand easily
With Best Regards
Rajesh Pandey
email :[email protected]
url :-- http://www.sixthquadrant.com
Mob :-- 9811903737
Delhi India -
How to get stateful and stateless session bean in second jsp
I create stateful session bean in the first jsp, then how can I get the stateful session bean in the second jsp? I find that somebody store the bean in HttpSession.
If I store the stateful session bean in HttpSession, then I can get it in the second jsp. My problem is that I can store the stateless session bean in HttpSession, and get it in the second jsp. Then, both stateful and stateless can maintain the state in the second jsp. What is the difference between stateful and stateless session bean in this case ?
I understand the definition of stateful and stateless session bean, but I'm confuse how to use session bean. Can anyone provide sample jsp to show difference of stateful and stateless? How the stateful session bean can maintain the state for the client?Greetings,
I create stateful session bean in the first jsp, then how can I get the stateful session bean in the
second jsp? I find that somebody store the bean in HttpSession.Which is the correct scope for sharing client-specific data when 'request' scope is insufficient.
If I store the stateful session bean in HttpSession, then I can get it in the second jsp. My problem is
that I can store the stateless session bean in HttpSession, and get it in the second jsp. Then, bothWhy is that a "problem"? Does your application not require the stateless bean to be shared? If so, then don't store the EJBObject reference in the session...
stateful and stateless can maintain the state in the second jsp. What is the difference betweenWhat do you mean by this exactly?..
stateful and stateless session bean in this case ?Statefulness of session beans is in regard to maintaining client state (er, in all cases). If your "stateless" bean is receiving information from the client (i.e. its caller) - either through a create method or a business method - and that information is available (retrievable from the bean) on subsequent method calls, then that bean is, in fact, stateful - regardless of how it is deployed.
I understand the definition of stateful and stateless session bean, but I'm confuse how to use
session bean.The correct question, it here seems, is "when" to use which type... Use a "stateful" bean when information about (from) the client (i.e. the caller) must be maintained across method calls of the bean. Use a "stateless" bean for general business methods that do not depend on "prior knowledge" of the client (i.e. the caller).
Can anyone provide sample jsp to show difference of stateful and stateless? How the statefulA "sample JSP" would yield nothing additional... The semantics of calling, using, and "persisting", bean references are always the same - regardless of type or class. However, the reason(s) for using one over the other depends entirely on the needs of your application.
session bean can maintain the state for the client?I recommend that you spend more time learning about EJBs generally. In particular, it seems you require more fundamental understanding of their scope and lifecycle. Refer to sections 4, 6, and 7 of the EJB 2.0 Specification.
Regards,
Tony "Vee Schade" Cook -
Probleme with transaction in session beans
Hello.
i create an session bean which call enties beans.
When i execute un example first time, its correct.
when i execute for second time, the methode don't stop.
i think it is problem of transaction.
thank youHi,
It is impossible to answer your with the given information. When ever you are asking a question please put the relavent informatin like code and deployment descriptors. So please do post the required information.
Ashok -
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 -
When a user logs out y proyect and go back to the sign up page, the sessionbean that contains the profile (int) stays with the same value, i have 6 variables (strings, int, integer, etc) in session bean, every time i use logout button i have to initialize the variables in session bean at once, i used sessionbean1.destroy(); but it doesnt work, anybody can tell me if im using well this?
The comments for the session bean's destroy method say:
* <p>This method is called when this bean is removed from
* session scope. Typically, this occurs as a result of
* the session timing out or being terminated by the application.</p>
* <p>You may customize this method to clean up resources allocated
* during the execution of the <code>init()</code> method, or
* at any later time during the lifetime of the application.</p>
*/This says that the web app automatically calls destroy() when the user session times out due to inactivity, or when the web application invalidates the session, such as, for example, by calling session.invalidate().
So, this does not appear to meet your needs as you want the variables to be nulled out when the user logs out (which does not necessarily end the session).
One other approach would be to create a session bean method, such as logout() that clear out the 6 variables.
Then have your logout button call this method, such as getSessionBean1().logout().
Another approach is to create a Java class, such as User with 6 properties.
Instantiate a User in the session bean when the user logs in
User user = new User();
and set user to null when the user logs out.
Maybe you are looking for
-
My ipod touch says connect to itunes and when i do it says error and it wont work hellllllpppppp
wheh
-
Why is the scan size of our epson 15Mb for PDF using image capture?
Hi All- This has been plaguing us since Snow Leopard when we lost the Epson Scanner tool from Epson to Image Capture scanning using our Epson 835 Artisan. PDF sizes are ridiculous using Image Capture. For example, 3 pages of text using Image Capture
-
How to get the WorkItem-ID in mapping.
Hi All, I have developed a BPM scenario ( R/3 proxy --> XI BPM --- > FTP )... in the runtime, the work item it will be generated. My requirement is the file name should be in the work item ID (I know how to set the file name dynamically in th
-
BC4J Custom Type Maps (MS-SQL cont.)
(FYI using JDeveloper 9.0.2.0.0, MS-SQL 2000 spk2 and MS-SQL's JDBC driver Version 2.2.0022) In the process of trying to get JDeveloper working fully with MS-SQL, I am at the point of developing a custom type map. Should this typemap include all mapp
-
Div's being pushed down in Safari
Hi guys, I've built a website for a client. For some unknown reason the footer content gets pushed down on the friends page in Safari and IE - all of the other pages are fine though. Here's a link to the site Can anyone see why this could be happenin