Runing EJB failed
I created a CMP entity EJB (from table) with Jdeveloper data wizard. I named it as MyCmpEJB. When I launch the EJB to run in the nested OC4J, OC4J report an error message--compiling--cmp field 'z?<L' can not find in the EJB impl class.
However, other CMP EJBs created by the same methods and steps can run successfully.
The difference between them is that the fields' name of the table that used to generate MyCmpEJB are in Chinese.
Why?
Thank you so much!
I created a CMP entity EJB (from table) with Jdeveloper data wizard. I named it as MyCmpEJB. When I launch the EJB to run in the nested OC4J, OC4J report an error message--compiling--cmp field 'z?<L' can not find in the EJB impl class.
However, other CMP EJBs created by the same methods and steps can run successfully.
The difference between them is that the fields' name of the table that used to generate MyCmpEJB are in Chinese.
Why?
Thank you so much!
Similar Messages
-
Deploying wl7 restriction : can't deploy ear if one ejb failed
In weblogic 6, I was able to deploy an ear even if one ejb of the ear could not
deploy. With weblogic 7 if one ejb failed, the all ear fail to deploy (There is
no cmr relation between those ejb). This a realy big restriction in development
mode, if you don't care about the failed ejb. You need to remove it from your
ear build and redeploy... Is there any way to have the same behaviour than in
wl6 ?
thank's
Nicolas FRANKIn weblogic 6, I was able to deploy an ear even if one ejb of the ear could not
deploy. With weblogic 7 if one ejb failed, the all ear fail to deploy (There is
no cmr relation between those ejb). This a realy big restriction in development
mode, if you don't care about the failed ejb. You need to remove it from your
ear build and redeploy... Is there any way to have the same behaviour than in
wl6 ?
thank's
Nicolas FRANK -
EJB fails to compile - static inner class problem
I am using OC4J 9.0.4 and Sun JDK1.4.2 and EJBs fail to compile if they reference objects that contain static inner classes. However, they successfully compile under JDK1.4.1.
For example, I have a class like below:
public class ValueObject
public static class Key
private Key key;
private String value;
Any references to ValueObject.Key inside the EJB cause the EJB compiler to generate "ValueObject$Key" which is incorrect. JDK1.4.1 is more lenient than 1.4.2, and allows this error through.
Is there a way around this problem other than reverting to JDK1.4.1?
Regards,
AndyThe reason I don't want to move to JDK 1.4.1 is because of the memory leak in the StringBuffer.toString() method.
Is there anywhere I can submit this as a bug?
Regards,
Andy -
Failover of SF EJB with ref to SL EJB fails
As a followon from my previous posting, we are also getting the
following failure:
Setup: A 2-server cluster (2xSolaris) running a web app, invoking a
stateful session EJB on a second 2-server cluster (Solaris & Win2K). (I
don't think the mixed architecture is significant). The stateful EJB can
also invoke a stateless EJB.
The first time the SF needs to invoke the SL, it looks up the home
interface, then the remote, and caches just the remote. If this code is
not executed, the SF EJB can fail to a secondary server ok. If it has
ever executed the SL code, the SF EJB cannot failover... The first
attempt to invoke it following the failover results in the following
exceptions (the first one expected as it detects the failure, the second
not expected). com.cp2.ejbsl is, surprisingly enough, the stateless EJB,
which it was NOT trying to use at the time:
Anyone got any clues?
TIA
Chris
####<01-Mar-01 15:04:57 GMT> <Error> <ConnectionManager> <lcy01fs01>
<WebAppFS> <ExecuteThread-9> <> <> <000000> <Could not connect to:
'5856064237335487305S:172.19.0.20:[8005,8005,7002,7002,8005,7002,-1]'>
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
at
weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
at
weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
at
weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:997)
at weblogic.rjvm.ConnectionManager.sendMsg(ConnectionManager.java:439)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:419)
at
weblogic.rjvm.MsgAbbrevOutputStream.flushAndSendRaw(MsgAbbrevOutputStream.java:114)
at
weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:122)
at
weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:144)
at
weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:84)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
at
com.cp2.ejbsfBeanEOImpl_WLStub.ejbsfResult(ejbsfBeanEOImpl_WLStub.java:175)
at com.cp1.rb1.executeAction(rb1.java:99)
at controller.doGet(controller.java:51)
at controller.doPost(controller.java:16)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:208)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1127)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1529)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<01-Mar-01 15:04:59 GMT> <Info> <cp1-rb1> <lcy01fs01> <WebAppFS>
<ExecuteThread-9> <> <> <000000> <Caught remote exception>
java.rmi.NoSuchObjectException: Activation failed with:
java.rmi.NoSuchObjectException: Unable to locate EJBHome:
'com.cp2.ejbsl' on server: 't3://172.19.0.20:8005
at
weblogic.ejb20.internal.HomeHandleImpl.getEJBHome(HomeHandleImpl.java:70)
at weblogic.ejb20.internal.HandleImpl.getEJBObject(HandleImpl.java:134)
at weblogic.ejb20.swap.EJBReplacer.resolveObject(EJBReplacer.java:84)
at
weblogic.common.internal.ReplacerObjectInputStream.resolveObject(ReplacerObjectInputStream.java:73)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:399)
at
java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2262)
at
java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at weblogic.ejb20.swap.PassivationUtils.read(PassivationUtils.java:52)
at
weblogic.ejb20.swap.ReplicatedMemorySwap.read(ReplicatedMemorySwap.java:111)
at
weblogic.ejb20.manager.StatefulSessionManager.getBean(StatefulSessionManager.java:173)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManager.java:231)
at
weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:113)
at
weblogic.ejb20.internal.StatefulEJBObject.preInvoke(StatefulEJBObject.java:136)
at com.cp2.ejbsfBeanEOImpl.ejbsfResult(ejbsfBeanEOImpl.java:23)
at
com.cp2.ejbsfBeanEOImpl_WLSkel.invoke(ejbsfBeanEOImpl_WLSkel.java:108)
at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at
weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:103)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at
weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:90)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
at
com.cp2.ejbsfBeanEOImpl_WLStub.ejbsfResult(ejbsfBeanEOImpl_WLStub.java:175)
at com.cp1.rb1.executeAction(rb1.java:99)
at controller.doGet(controller.java:51)
at controller.doPost(controller.java:16)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:208)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1127)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1529)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Hmmm. Similar in that it relates to failover, but it does seem to be quite a
different problem. It's more closely related to my previous post (problem in
failBACK). However in neither case am I using an EJB handle, just the remote
reference.
Chris
Diego Doval wrote:
> I'm seeing something very similar, where the first failover works but
> subsequent failovers don't. Apparently when the second server goes back
> online it doesn't replicate the state so a call still looks for the old
> reference and hence the ConnectionException.
>
> The problem I had before (see my message from a few hours ago) is related to
> using the EJB handle, using a Remote Reference instead works fine. The fact
> that using the handle breaks it is probably a bug.
>
> If anybody knows more about this ConnectionException problem, it would be
> greatly appreciated.
>
> thanks,
>
> diego
>
> "Chris Palmer" <[email protected]> wrote in message
> news:[email protected]...
> > As a followon from my previous posting, we are also getting the
> > following failure:
> >
> > Setup: A 2-server cluster (2xSolaris) running a web app, invoking a
> > stateful session EJB on a second 2-server cluster (Solaris & Win2K). (I
> > don't think the mixed architecture is significant). The stateful EJB can
> > also invoke a stateless EJB.
> >
> > The first time the SF needs to invoke the SL, it looks up the home
> > interface, then the remote, and caches just the remote. If this code is
> > not executed, the SF EJB can fail to a secondary server ok. If it has
> > ever executed the SL code, the SF EJB cannot failover... The first
> > attempt to invoke it following the failover results in the following
> > exceptions (the first one expected as it detects the failure, the second
> > not expected). com.cp2.ejbsl is, surprisingly enough, the stateless EJB,
> > which it was NOT trying to use at the time:
> >
> > Anyone got any clues?
> >
> > TIA
> > Chris
> >
> > ####<01-Mar-01 15:04:57 GMT> <Error> <ConnectionManager> <lcy01fs01>
> > <WebAppFS> <ExecuteThread-9> <> <> <000000> <Could not connect to:
> > '5856064237335487305S:172.19.0.20:[8005,8005,7002,7002,8005,7002,-1]'>
> > java.net.ConnectException: Connection refused
> > at java.net.PlainSocketImpl.socketConnect(Native Method)
> > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
> > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
> > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
> > at java.net.Socket.<init>(Socket.java:273)
> > at java.net.Socket.<init>(Socket.java:127)
> > at weblogic.rjvm.t3.T3JVMConnection.newSocket(T3JVMConnection.java:324)
> >
> > at
> >
> weblogic.rjvm.t3.T3JVMConnection.newSocketWithRetry(T3JVMConnection.java:312
> )
> >
> > at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:74)
> > at
> >
> weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:148)
> >
> > at weblogic.rjvm.Protocol.createConnection(Protocol.java:201)
> > at
> >
> weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.jav
> a:997)
> >
> > at weblogic.rjvm.ConnectionManager.sendMsg(ConnectionManager.java:439)
> > at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:419)
> > at
> >
> weblogic.rjvm.MsgAbbrevOutputStream.flushAndSendRaw(MsgAbbrevOutputStream.ja
> va:114)
> >
> > at
> >
> weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:
> 122)
> >
> > at
> >
> weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:144)
> >
> > at
> >
> weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRe
> quest.java:84)
> >
> > at
> >
> weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
> :247)
> >
> > at
> >
> weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
> :225)
> >
> > at
> >
> com.cp2.ejbsfBeanEOImpl_WLStub.ejbsfResult(ejbsfBeanEOImpl_WLStub.java:175)
> >
> > at com.cp1.rb1.executeAction(rb1.java:99)
> > at controller.doGet(controller.java:51)
> > at controller.doPost(controller.java:16)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > at
> >
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :208)
> >
> > at
> >
> weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> ntext.java:1127)
> >
> > at
> >
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> :1529)
> >
> > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >
> > ####<01-Mar-01 15:04:59 GMT> <Info> <cp1-rb1> <lcy01fs01> <WebAppFS>
> > <ExecuteThread-9> <> <> <000000> <Caught remote exception>
> > java.rmi.NoSuchObjectException: Activation failed with:
> > java.rmi.NoSuchObjectException: Unable to locate EJBHome:
> > 'com.cp2.ejbsl' on server: 't3://172.19.0.20:8005
> > at
> > weblogic.ejb20.internal.HomeHandleImpl.getEJBHome(HomeHandleImpl.java:70)
> >
> > at weblogic.ejb20.internal.HandleImpl.getEJBObject(HandleImpl.java:134)
> >
> > at weblogic.ejb20.swap.EJBReplacer.resolveObject(EJBReplacer.java:84)
> > at
> >
> weblogic.common.internal.ReplacerObjectInputStream.resolveObject(ReplacerObj
> ectInputStream.java:73)
> >
> > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:399)
> > at
> > java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2262)
> > at
> > java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
> > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
> > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
> > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
> > at weblogic.ejb20.swap.PassivationUtils.read(PassivationUtils.java:52)
> > at
> >
> weblogic.ejb20.swap.ReplicatedMemorySwap.read(ReplicatedMemorySwap.java:111)
> >
> > at
> >
> weblogic.ejb20.manager.StatefulSessionManager.getBean(StatefulSessionManager
> .java:173)
> >
> > at
> >
> weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
> er.java:231)
> >
> > at
> > weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:113)
> > at
> >
> weblogic.ejb20.internal.StatefulEJBObject.preInvoke(StatefulEJBObject.java:1
> 36)
> >
> > at com.cp2.ejbsfBeanEOImpl.ejbsfResult(ejbsfBeanEOImpl.java:23)
> > at
> > com.cp2.ejbsfBeanEOImpl_WLSkel.invoke(ejbsfBeanEOImpl_WLSkel.java:108)
> > at
> >
> weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
> >
> > at
> >
> weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
> :128)
> >
> > at
> >
> weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
> >
> > at
> >
> weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
> java:103)
> >
> > at
> >
> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
> 7)
> >
> > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> > at
> >
> weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRe
> quest.java:90)
> >
> > at
> >
> weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
> :247)
> >
> > at
> >
> weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
> :225)
> >
> > at
> >
> com.cp2.ejbsfBeanEOImpl_WLStub.ejbsfResult(ejbsfBeanEOImpl_WLStub.java:175)
> >
> > at com.cp1.rb1.executeAction(rb1.java:99)
> > at controller.doGet(controller.java:51)
> > at controller.doPost(controller.java:16)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > at
> >
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :208)
> >
> > at
> >
> weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> ntext.java:1127)
> >
> > at
> >
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> :1529)
> >
> > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >
> >
-
Hi,
I am moving an legacy application which consist of EJB 2.0 from Weblogic 9 to weblogic 10.3.4 and I am facing following problem:
Caused by: java.lang.AssertionError: Failed to generate class for com.sky.jak.portfolio.beans.PortfolioRetriever_dqv50s_EOImpl_1034_WLStub
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:797)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:786)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:74)
at weblogic.rmi.internal.StubInfo.resolveObject(StubInfo.java:267)
at weblogic.rmi.internal.StubInfo.readResolve(StubInfo.java:199)
at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.rmi.extensions.server.CBVInputStream.readObject(CBVInputStream.java:64)
at weblogic.rmi.internal.ServerRequest.unmarshalReturn(ServerRequest.java:100)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at com.sky.jak.portfolio.beans.PortfolioRetriever_dqv50s_HomeImpl_1034_WLStub.create(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sky.jak.common.servicelocator.ServiceLocatorImp.callCreateMethod(ServiceLocatorImp.java:246)
at com.sky.jak.common.servicelocator.ServiceLocatorImp.getBean(ServiceLocatorImp.java:211)
at com.sky.jak.common.servicelocator.RemoteInvocationHandler.doReinitializeDelegate(RemoteInvocationHandler.java:155)
at com.sky.jak.common.proxy.RecoverableInvocationHandler.reinitializeDelegate(RecoverableInvocationHandler.java:357)
... 13 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:795)
... 37 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: 6
at com.sky.jak.portfolio.beans.PortfolioRetriever_dqv50s_EOImpl_1034_WLStub.ensureInitialized(Unknown Source)
at com.sky.jak.portfolio.beans.PortfolioRetriever_dqv50s_EOImpl_1034_WLStub.<init>(Unknown Source)
... 42 more
When I run appc at compile time I am getting the reported error. What strang is that if I disable appc at compile time, weblogic performs appc on the fly and all works fine. The same error I get even when I do run appc externaly to final ear.
Can someone please assist to troubleshoot that?
Thanks
Edited by: user13047709 on Dec 12, 2012 2:26 AMHi,
the full stack trace follows:
2012-12-11 13:54:53,411 ERROR [MSR !f6251134-4a63-49f9-9366-ee1713fa9bbb,f6251134-4a63-49f9-9366-ee1713fa9bbb,2370dbe6-f974-426d-8191-459f9cbd233a,JSP,JSKY,SKY,1,3! ] msengine.MSEngineBean - JSKY SKY error
com.sky.jak.marketstructure.universe.UniverseRetrieverException: [Market Structure Exception] Market Structure Wrapped Exception cause: Throwable thrown within Portfolio: 6
at com.sky.jak.marketstructure.universe.UniverseRetriever.getPortfolioUniverse(UniverseRetriever.java:638)
at com.sky.jak.marketstructure.report.StatsFieldCalculator.loadData(StatsFieldCalculator.java:162)
at com.sky.jak.marketstructure.report.UniverseFieldCalculator$CalcThread.run(UniverseFieldCalculator.java:167)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at com.sky.jak.common.concurrent.ExecutorFacade$1.call(ExecutorFacade.java:127)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.sky.jak.common.servicelocator.ServiceLocatorException: com.sky.jak.portfolio.exception.PortfolioThrowableWrapperException: 6
at com.sky.jak.common.servicelocator.ServiceLocator.getPortfolioRetriever(ServiceLocator.java:769)
at com.sky.jak.marketstructure.universe.UniverseRetriever.getPortfolioUniverse(UniverseRetriever.java:584)
... 9 more
Caused by: com.sky.jak.portfolio.exception.PortfolioThrowableWrapperException: 6
at com.sky.jak.common.proxy.PointExceptionFactory.getDefaultCheckedException(PointExceptionFactory.java:195)
at com.sky.jak.common.proxy.PointExceptionFactory.getCheckedException(PointExceptionFactory.java:100)
at com.sky.jak.common.proxy.RecoverableOperationState.throwThrowable(RecoverableOperationState.java:349)
at com.sky.jak.common.proxy.RecoverableOperationState.throwThrowable(RecoverableOperationState.java:339)
at com.sky.jak.common.proxy.RecoverableOperationState.getEntry(RecoverableOperationState.java:277)
at com.sky.jak.common.proxy.RecoverableOperationState.processThrowable(RecoverableOperationState.java:175)
at com.sky.jak.common.proxy.RecoverableOperationState.processThrowableAndThrowIfMaxReached(RecoverableOperationState.java:132)
at com.sky.jak.common.proxy.RecoverableInvocationHandler.reinitializeDelegate(RecoverableInvocationHandler.java:380)
at com.sky.jak.common.servicelocator.RemoteInvocationHandler.<init>(RemoteInvocationHandler.java:59)
at com.sky.jak.common.servicelocator.ServiceLocatorImp.getLocatableService(ServiceLocatorImp.java:134)
at com.sky.jak.common.servicelocator.ServiceLocator.getPortfolioRetriever(ServiceLocator.java:765)
... 10 more
Caused by: java.lang.AssertionError: Failed to generate class for com.sky.jak.portfolio.beans.PortfolioRetriever_dqv50s_EOImpl_1034_WLStub
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:797)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:786)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:74)
at weblogic.rmi.internal.StubInfo.resolveObject(StubInfo.java:267)
at weblogic.rmi.internal.StubInfo.readResolve(StubInfo.java:199)
at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.rmi.extensions.server.CBVInputStream.readObject(CBVInputStream.java:64)
at weblogic.rmi.internal.ServerRequest.unmarshalReturn(ServerRequest.java:100)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at com.sky.jak.portfolio.beans.PortfolioRetriever_dqv50s_HomeImpl_1034_WLStub.create(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sky.jak.common.servicelocator.ServiceLocatorImp.callCreateMethod(ServiceLocatorImp.java:246)
at com.sky.jak.common.servicelocator.ServiceLocatorImp.getBean(ServiceLocatorImp.java:211)
at com.sky.jak.common.servicelocator.RemoteInvocationHandler.doReinitializeDelegate(RemoteInvocationHandler.java:155)
at com.sky.jak.common.proxy.RecoverableInvocationHandler.reinitializeDelegate(RecoverableInvocationHandler.java:357)
... 13 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:795)
... 37 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: 6
at com.sky.jak.portfolio.beans.PortfolioRetriever_dqv50s_EOImpl_1034_WLStub.ensureInitialized(Unknown Source)
at com.sky.jak.portfolio.beans.PortfolioRetriever_dqv50s_EOImpl_1034_WLStub.<init>(Unknown Source)
... 42 more
Ant appc targed follows:
<target name="appc" unless="skip-appc">
<property name="appc.target" value="${svc.jar.name}.ear"/>
<echo message="${toString:wl.class.path}"/>
<mkdir dir="${appc.dir}"/>
<java classname="weblogic.appc" dir="${dist.dir}" fork="true" failonerror="true">
<jvmarg value="-Djava.io.tmpdir=${appc.dir}"/>
<arg line="-verbose"/>
<classpath>
<path refid="wl.class.path"/>
</classpath>
<arg value="${appc.target}"/>
</java>
<delete dir="${appc.dir}"/>
</target>
While running ant JAVA_HOME is set to JDK 1.6, wl.class.path is pointing to weblogic 10.3.4 libraries. Now I am just thinking of that ear is compiled by JDK 1.6 with target specified to 1.5. Do I somehow specify the same option for appc ? -
EJBs failing to Load into 8.1.6
Oracle Java gurus:
I have a similar problem with loading EJBs into 8.1.6.
However the problem occurs when loading from the demo examples on Solaris as well as loading from JDeveloper 3.1.1.2.
When the database has been initially built, everything works fine. However, after loading in a vendor jar file I get the following erros on any subsequent ejb loading:
Reading Deployment Descriptor...done
Verifying Deployment Descriptor...done
Gathering users...done
Generating Comm Stubs.....................................done
Compiling Stubs...done
Generating Jar File...done
Loading EJB Jar file and Comm Stubs Jar file...done
Generating EJBHome and EJBObject on the server...
An unexpected exception occurred deserializing deployment descriptor: null
*** Error code 1
make: Fatal error: Command failed for target `server_generated.jar'
I did find out from the vendor that the java classes were developed (and therefore compiled) using jdk 1.3.
A large number of these classes load as invalid since they have gui elements. In my application, the gui elements will never be realized, so I atte,pted to marke them valid through loadjava using a resolver spec with (* -) in the spec, bu that failed to resolve the classes.
Is the byte code in jdk 1.3 that different as to wound Oracle? I deleted the invalid java classes, but that was insufficient to heal this problem. Do I need to delete all of the java 1.3 classes in the database and run initjvm again? How do I fix this problem?
- KenOracle Java gurus:
I have a similar problem with loading EJBs into 8.1.6.
However the problem occurs when loading from the demo examples on Solaris as well as loading from JDeveloper 3.1.1.2.
When the database has been initially built, everything works fine. However, after loading in a vendor jar file I get the following erros on any subsequent ejb loading:
Reading Deployment Descriptor...done
Verifying Deployment Descriptor...done
Gathering users...done
Generating Comm Stubs.....................................done
Compiling Stubs...done
Generating Jar File...done
Loading EJB Jar file and Comm Stubs Jar file...done
Generating EJBHome and EJBObject on the server...
An unexpected exception occurred deserializing deployment descriptor: null
*** Error code 1
make: Fatal error: Command failed for target `server_generated.jar'
I did find out from the vendor that the java classes were developed (and therefore compiled) using jdk 1.3.
A large number of these classes load as invalid since they have gui elements. In my application, the gui elements will never be realized, so I atte,pted to marke them valid through loadjava using a resolver spec with (* -) in the spec, bu that failed to resolve the classes.
Is the byte code in jdk 1.3 that different as to wound Oracle? I deleted the invalid java classes, but that was insufficient to heal this problem. Do I need to delete all of the java 1.3 classes in the database and run initjvm again? How do I fix this problem?
- Ken -
Is there any standard way or testing utility for EJB fail safe in cluster env
Hi
I got to test the beans for complete fail safe like home
fail overing and method calls (idempodentcy) fail over, is there
any testing utility or standard approach for this or I got to do
it manually??
any help on this highly appriciated
Thanks and regards
Aruna
Look for solutions here:
https://discussions.apple.com/docs/DOC-3521
https://discussions.apple.com/docs/DOC-3353
Ciao. -
Hi, Dear All:
I caught this error while I was deploying a EJB to a Sun one 8 application server.
[|[#|2004-06-24T12:52:18.927+1000|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=14;|Caught java.lang.RuntimeException while processing CMP beans for application [wsc]; module [uidgen-ejb.jar]: JDO71002: The schema file wsc_uidgen-ejb, does not contain a table named Counter. See log for details.
java.lang.RuntimeException: JDO71002: The schema file wsc_uidgen-ejb, does not contain a table named Counter
at com.sun.jdo.api.persistence.mapping.ejb.MappingFile.intoMappingClasses(MappingFile.java:160)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.loadMappingClasses(MappingGenerator.java:429)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.generateMapping(MappingGenerator.java:267)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.loadOrCreateMappingClasses(JDOCodeGenerator.java:500)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCodeGenerator.java:145)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCodeGenerator.java:118)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:143)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:38)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:92)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:69)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:768)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:289)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:311)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:205)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:283)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:102)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:192)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:261)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:215)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:583)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:200)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:180)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:582)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:161)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:156)
at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:154)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:569)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:979)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:211)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:692)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:647)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:589)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:691)
at java.lang.Thread.run(Thread.java:534)
|#]
Please Note that I wrote the Sun one cmp mappings by myself, and the mapping files is like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 8.0 EJB 2.1//EN" "http://www.sun.com/software/sunone/appserver/dtds/sun-cmp-mappings_1_1.dtd">
<sun-cmp-mappings>
<sun-cmp-mapping>
<schema/>
<entity-mapping>
<ejb-name>CounterEJB</ejb-name>
<table-name>Counter</table-name>
<cmp-field-mapping>
<field-name>name</field-name>
<column-name>Counter.Name</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>counter</field-name>
<column-name>Counter.CounterValue</column-name>
</cmp-field-mapping>
</entity-mapping>
</sun-cmp-mapping>
</sun-cmp-mappings>
Could Anybody help?
ThanksLooking a the sun-cmp-mapping.xml file that you show, the <schema> element is empty thus leaving the creation of the dbschema file to be generated during deployment. Does your XP box point to the same DB? Are the DB tables created prior to deployment of the app?
-
Hello,
I have installed JDeveloper 9.0.3 on windows. I created a workspace and sample project for testing. Added a CMP EJB (Dept) using JDevs "create EJB from table option", added a client to test the EJB using JDevs 'New Sample Client" option, compiled the project and ran the sample client. I get the following error in the embedded OC4J
javax.naming.NameNotFoundException: Dept not found
java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
I have not changed any bit of configuration and code generated by JDev.
I tried this because I was getting the same error in a working project imported from other machine.
Any solution?
Thanks in advance.
NAGFirst you need to run the EJB and then run the client.
Here is something to guide you:
http://otn.oracle.com/products/jdev/htdocs/handson/j2ee/j2ee13hos.html#lab2
By the way, why are you using such an old version of JDeveloper? Isn't it time to upgrade to 9.0.5 or at least 9.0.4? -
PI2.1 : Cannot make Configuration Archive : Fetch Runing/Start Fail
Hello,
I cannot make a configuration archive with PI2.1.
I'm using PI2.1 to control WLC.
When I run Configuration archive, it says Fetch Running: "Unkown error", Fetch Startup "Unknown Error", Fetch VLAN "Unknown Error".
What should be the reason?
I can enter in the WLC, configure it from PI, but cannot make "Archive Config"
Please help.
Regards,Please check the following:
SWIM and Configuration Archives support for Devices during Cisco Prime Infrastructure releases—Table 4 outlines the devices that the software image management and configuration archives support during the various Prime Infrastructure releases.
Table 4 SWIM and Configuration Archives support for Devices during Prime Infrastructure Releases
Devices
Prime Infrastructure Releases
Cisco 4400 Wireless LAN Controller1
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 5500 Series Wireless LAN Controllers
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco WiSM1 Controller
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 2106 Wireless LAN Controller1
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 2504 Wireless LAN Controller
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 2800 and 3800 Series Integrated Services Routers
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco Flex 7500 Series Wireless LAN Controller
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 8500 Wireless LAN Controller1
1.4, 2.0, and 2.1
Cisco Virtual Wireless LAN Controller1
1.4, 2.0, and 2.1
Cisco WiSM2 Controller
Not supported
1.Prime Infrastructure 1.4 does not support SWIM in Cisco 2106/4400/8500/WiSM2/Virtual WLC.
Hope that helps. -
Static inner class causes deployment on OC4J 10.1.2 to fail
Hi,
this issue has already been raised on OC4J 9.0.4 with J2SDK 1.4.2 (see EJB fails to compile - static inner class problem
Recap: When referencing static inner classes in an EJB, the deployment fails. During the generation of the wrapper classes, a signature <package>.<outer class>.<inner class> gets converted to <package>.<outer class>$<inner class>, which is syntactically wrong. While the Java 1.4.1 compiler kindly ignores this syntax error, its 1.4.2 counterpart complains - and fails.
@Oracle: When will this bug be fixed for OC4J 10.1.2?
Best regards,
HolgerHolger,
Don't static inner classes contradict the EJB specification?
In any case, in answer to Andy's question: If you wish to file this as a bug, you can do so via the MetaLink Web site.
[In fact, [i]MetaLink is your only option for submitting bugs for Oracle products -- as far as I know.]
Good Luck,
Avi. -
Background job failing with license check error
Hi Experts
In our ERP 6.0 system ,all the background jobs are failing with license check error.
Have checked the license in SLICENSE and the license is fine.
There is no warning while users are loggign in ,but when any background job is runing its failing with error
Job started
Logon not possible (error in license check)
Job cancelled after system exception ERROR_MESSAGE
Also performed the license test which is failing
F:\usr\sap\XX1\SYS\exe\uc\NTAMD64>saplicense -test pf=F:\usr\sap\XX1\SYS\profile
\XX1_DVEBMGS00_host_xx
Protocol saplicense test:
Read sapsytem name
ok, sapsytem name = XX1
Read message server host
ok, host = hostname
Read message server service port
ok, service port = sapmsXX1
Connect to message server
ok, connect done
Read hardware key from message server
ok, got hardware key
Detach from message server
ok, detached
Check hardware key
ok, hardware key = T0343073854
Connect to database
ok, connected
Check license
ok, check done
Disconnect database
ok, database disconnected
test result: license test failed
LICENSE system: XX1 hardware key: T0343073854 expiration_date:
installation no: key:
userlimit: 0 productid: R3_BASIS
system-nr:
license expired ***
Please suggest how to troubleshoot.
Regards
Ajay@Michael
In SLICENSe the Hardware key field is not BLUE or BLACK and its showing the exact hardware key which i can see at OS level with saplicense -get command.
@Jagadish
Note is good refrence, i reiinstalled the Digitally signed license with saplikey command and it was successful.
But still the license test is failing at OS Level..below is the command prompt output.
===================================================================
F:\usr\sap\XX1\SYS\exe\uc\NTAMD64>saplikey -install C:\license_script_XX.txt pf
=F:\usr\sap\XX\SYS\profile\XX_DVEBMGS00_mngsez148079
SAP License Key Administration - Copyright (C) 2003 SAP AG
2 SAP license key(s) successfully installed.
F:\usr\sap\XX\SYS\exe\uc\NTAMD64>saplicense -test pf=F:\usr\sap\XX1\SYS\profile
\MD1_DVEBMGS00_mngsez148079
Protocol saplicense test:
Read sapsytem name
ok, sapsytem name = XX1
Read message server host
ok, host = host
Read message server service port
ok, service port = sapmsXX1
Connect to message server
ok, connect done
Read hardware key from message server
ok, got hardware key
Detach from message server
ok, detached
Check hardware key
ok, hardware key = T0343073854
Connect to database
ok, connected
Check license
ok, check done
Disconnect database
ok, database disconnected
test result: license test failed
LICENSE system: XX1 hardware key: T0343073854 expiration_date:
installation no: key:
userlimit: 0 productid: R3_BASIS
system-nr:
license expired ***
============================================================
@Juan
The hardware key was changed and we requested a new license with new hardware key,system was runing fine for couple of weeks with all background jiobs for SPAM./SAINT Ok .We performed EHP4 on this system.
But now this issue is here,so i guess we should troubleshoot.
Please let me know any other pointers.
Regards
Ajay
PS In SLICENSE new installed license is fine and all users can login. -
Persistance layer failed to deploy
Hi,
When I try to build using ant file I am getting the following exception in WLS8.1
[java] [EJB:011016]The persistence layer of the Entity EJB failed to deploy.
[java] [EJB:011018]The file weblogic-cmp-rdbms-jar.xml, specified in a type-storage
element of your weblogic-ejb-jar.xml descriptor, does not exi
the JAR file.
[java] at weblogic.ejb20.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:469)
My weblogic-ejb-jar.xml file is :
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd" >
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>UserCheck</ejb-name>
<jndi-name>Gateway_UC_Home</jndi-name>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Log</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>ramtopic1</destination-jndi-name>
</message-driven-descriptor>
<jndi-name>Log</jndi-name>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>GatewayUpdate</ejb-name>
<entity-descriptor>
<entity-cache>
<max-beans-in-cache>1000</max-beans-in-cache>
</entity-cache>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>7.0</type-version>
<type-storage>weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
</persistence>
</entity-descriptor>
<jndi-name>RemoteMsg_Update_Home</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
My weblogic-cmp-rdbms-jar.xml file is:
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls810/dtd/weblogic-rdbms20-persistence-810.dtd'>
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
<ejb-name>GatewayUpdate</ejb-name>
<data-source-name>gatewayPool</data-source-name>
<table-name>textsms</table-name>
<field-map>
<cmp-field>user</cmp-field>
<dbms-column>user</dbms-column>
</field-map>
<field-map>
<cmp-field>msgid</cmp-field>
<dbms-column>msgid</dbms-column>
</field-map>
<field-map>
<cmp-field>msg</cmp-field>
<dbms-column>msg</dbms-column>
</field-map>
<field-map>
<cmp-field>org</cmp-field>
<dbms-column>org</dbms-column>
</field-map>
<field-map>
<cmp-field>mno</cmp-field>
<dbms-column>mno</dbms-column>
</field-map>
<field-map>
<cmp-field>status</cmp-field>
<dbms-column>status</dbms-column>
</field-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>False</create-default-dbms-tables>
</weblogic-rdbms-jar>
Pl.suggest.
RamHi,
I hv found out the issue.I hv not added one element tag in weblogic-cmp-rdbms-xml.jar.After
adding the same the above error did not come.But when I create ear file I hv got
another exception saying the jar file mentioned is not aval in the ear file.
Below is the console output:
Gateway.jar:
[echo] creating basic ejb jar file ...
[jar] Building jar: E:\myejb\staging\Gateway.jar
[echo] ... done.
[echo] appc'ing the ejb jar file ...
[echo] appc'ing the ejb jar file ...
[java] [appc] Created working directory: C:\DOCUME~1\ram\LOCALS~1\Temp\appcgen
[java] [J2EE:160120]Error: The module, 'Gateway.jar', is declared in the
application.xml descriptor but cannot be found in the ear file.
BUILD FAILED
file:E:/myejb/build.xml:95: Java returned: 1
My build file is :
<!--
This file builds the EAR file for the SessBean.
Invoke this file by providing the base directory of the weblogic
installation. This can be done by using the following command
line:
ant -f build.xml -Dwlhome=f:\bea\weblogic81
Before invoking ant, make sure that the optional.jar file
has been copied into the lib directory of your ant installation.
-->
<project name="GatewayBean" default="all">
<target name="init">
<property name="srcdir" value="."/>
<property name="java.classpath"
value="${wlhome}${file.separator}server${file.separator}lib${file.separator}weblogic.jar"/>
<delete dir="classes"
includeEmptyDirs="true"
failonerror="false" />
<delete dir="staging"
includeEmptyDirs="true"
failonerror="false"/>
<echo message="creating staging area ..."/>
<mkdir dir="staging"/>
<echo message=" ... done."/>
<!-- Define the WebLogic appc task -->
<echo message="defining weblogic appc task ..."/>
<taskdef name="appc"
classname="weblogic.ant.taskdefs.j2ee.Appc"
classpath="${java.classpath}"/>
<echo message=" ... done."/>
</target>
<!-- target compiles all required classes -->
<target name="compile" depends="init">
<mkdir dir="classes"/>
<echo message="compiling all sources ... "/>
<javac srcdir="${srcdir}"
destdir="classes"
verbose="no"
classpath="${java.classpath}" />
<echo message=" ... done."/>
</target>
<!-- target builds the jar file containing JSP helper classes -->
<target name="JSPClasses.jar" depends="compile">
<echo message="creating JSPClasses.jar ... "/>
<jar jarfile="staging${file.separator}JSPClasses.jar">
<fileset dir="classes" includes="**/JSP*.class"/>
</jar>
<echo message=" ... done."/>
</target>
<!-- target builds the war file containing the web application -->
<target name="Gateway.war" depends="init,JSPClasses.jar">
<echo message="creating web archive ... "/>
<war destfile="staging${file.separator}Gateway.war"
webxml="web.xml" >
<fileset dir="${srcdir}">
<include name="*.jsp"/>
<include name="*.html"/>
</fileset>
<lib dir="staging" includes="JSPClasses.jar"/>
</war>
<echo message=" ... done."/>
</target>
<!-- target builds the jar file containing all the EJBs -->
<target name="Gateway.jar" depends="compile">
<!-- First jar up the basic classes required for the EJBs -->
<echo message="creating basic ejb jar file ... "/>
<jar jarfile="staging${file.separator}Gateway.jar">
<zipfileset dir="."
prefix="META-INF"
includes="*.xml"/>
<fileset dir="classes"
excludes="**/JSP*.class"/>
</jar>
<echo message=" ... done."/>
<!-- Next appc the jar file to ejb compile the ejbs-->
<echo message="appc'ing the ejb jar file ... "/>
<!-- Next appc the jar file to ejb compile the ejbs-->
<echo message="appc'ing the ejb jar file ... "/>
<java classname="weblogic.appc"
failonerror="true"
fork="true"
classpath="${java.classpath}">
<arg line="-basicClientJar -verbose -forceGeneration -classpath ${java.classpath}
staging${file.separator}Gateway.jar"/>
</java>
<echo message=" ... done."/>
<!--
<java classname="weblogic.appc"
failonerror="true"
fork="true"
classpath="${java.classpath}">
<arg line="-basicClientJar -verbose -forceGeneration -classpath ${java.classpath}
staging${file.separator}Gateway.jar"/>
</java>
-->
<echo message=" ... done."/>
</target>
<!-- target builds the EAR file -->
<target name="Gateway.ear"
depends="init,Gateway.war,Gateway.jar">
<echo message="creating enterprise archive ... "/>
<jar jarfile="Gateway.ear">
<zipfileset dir="."
prefix="META-INF"
includes="application.xml"/>
<fileset dir="staging"
includes="Gateway.war,Gateway.jar"/>
</jar>
<echo message=" ... done."/>
</target>
<!--
<target name="cleanup">
<echo message="cleaning up ... "/>
<delete dir="staging"
includeEmptyDirs="true"
failonerror="false"/>
<delete dir="classes"
includeEmptyDirs="true"
failonerror="false"/>
<echo message=" ... done."/>
</target>
-->
<target name="all" depends="init, Gateway.ear">
<echo message="Done building ./Gateway.ear"/>
</target>
</project>
My application.xml file is :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application
1.3//EN' 'http://java.sun.com/dtd/application_1_3.dtd'>
<application>
<display-name>Gateway</display-name>
<description>Gateway</description>
<module>
<ejb>Gateway.jar</ejb>
</module>
</application>
After doing jar tvf :
GMT+05:30 2004 META-INF/
GMT+05:30 2004 META-INF/MANIFEST.MF
GMT+05:30 2004 META-INF/Copy of build.xml
GMT+05:30 2004 META-INF/ejb-jar.xml
GMT+05:30 2004 META-INF/build.xml
GMT+05:30 2004 META-INF/application.xml
GMT+05:30 2004 META-INF/web.xml
GMT+05:30 2004 META-INF/weblogic-cmp-rdbms-jar.xml
GMT+05:30 2004 META-INF/weblogic-ejb-jar.xml
GMT+05:30 2004 gateway/
GMT+05:30 2004 gateway/LogBean.class
GMT+05:30 2004 gateway/Gateway_UC.class
GMT+05:30 2004 gateway/Gateway_UC_Home.class
GMT+05:30 2004 gateway/Gateway_UC_Bean.class
GMT+05:30 2004 gateway/Msg_Update.class
GMT+05:30 2004 gateway/Msg_Update_Home.class
GMT+05:30 2004 gateway/Msg_Update_Bean.class
GMT+05:30 2004 gateway/UpdatePK.class
Pl.advise.
Ram
Rob Woollen <[email protected]> wrote:
I'd suggest you build the CMP example that ships with WLS. Then compare
the structure of its ejb-jar with your application.
If you're still having problems, can you show me the output of jar tvf
on your ejb-jar file? It's looking for the CMP descriptor in the
META-INF directory.
-- Rob
Ram wrote:
Hi,
When I try to build using ant file I am getting the following exceptionin WLS8.1
[java] [EJB:011016]The persistence layer of the Entity EJB failedto deploy.
[java] [EJB:011018]The file weblogic-cmp-rdbms-jar.xml, specified ina type-storage
element of your weblogic-ejb-jar.xml descriptor, does not exi
the JAR file.
[java] at weblogic.ejb20.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:469)
My weblogic-ejb-jar.xml file is :
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic8.1.0 EJB//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd" >
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>UserCheck</ejb-name>
<jndi-name>Gateway_UC_Home</jndi-name>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Log</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>ramtopic1</destination-jndi-name>
</message-driven-descriptor>
<jndi-name>Log</jndi-name>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>GatewayUpdate</ejb-name>
<entity-descriptor>
<entity-cache>
<max-beans-in-cache>1000</max-beans-in-cache>
</entity-cache>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>7.0</type-version>
<type-storage>weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
</persistence>
</entity-descriptor>
<jndi-name>RemoteMsg_Update_Home</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
My weblogic-cmp-rdbms-jar.xml file is:
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls810/dtd/weblogic-rdbms20-persistence-810.dtd'>
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
<ejb-name>GatewayUpdate</ejb-name>
<data-source-name>gatewayPool</data-source-name>
<table-name>textsms</table-name>
<field-map>
<cmp-field>user</cmp-field>
<dbms-column>user</dbms-column>
</field-map>
<field-map>
<cmp-field>msgid</cmp-field>
<dbms-column>msgid</dbms-column>
</field-map>
<field-map>
<cmp-field>msg</cmp-field>
<dbms-column>msg</dbms-column>
</field-map>
<field-map>
<cmp-field>org</cmp-field>
<dbms-column>org</dbms-column>
</field-map>
<field-map>
<cmp-field>mno</cmp-field>
<dbms-column>mno</dbms-column>
</field-map>
<field-map>
<cmp-field>status</cmp-field>
<dbms-column>status</dbms-column>
</field-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>False</create-default-dbms-tables>
</weblogic-rdbms-jar>
Pl.suggest.
Ram -
Migrating from 903 to 904: what changed in JNDI calls to EJB's and topics
Hello all,
Ok,
First of all this all works fine in 903, the problem is occuring when I try to deploy our appliction on 904.
My problem is that the web tier can't find references to ejb's and my MDB fails at deployment because the reference to the topic fails.
Here are the error messages:
1.
Error loading package at file:/C:/Oracle/904Prod/j2ee/home/applications/sdr/ejb/SDRSysAlertMDB/, Error deploying file:/C:/Oracle/904Prod/j2ee/home/applications/sdr/ejb/SDRSysAlertMDB/ homes: No location set for Topic resource MessageDrivenBean SDRSysAlertMDB
2.
Error instantiating web-app JNDI-context: No location specified and no suitable instance of the type 'ControllerEJB' found for the ejb-ref ejb/ControllerEJB
And ideas of where to look would be appreciated.
Thanks
MattSteve, thanks for your quick response. I have 2 problems here.
What we are covering is the MDB problem below. I'll start with that one first and then work on the web tier referencing the EJB failing problem later.
Short answer is yes I have those attributes. Here are my (edited)config files.
EJB-JAR.XML
<ejb-jar>
<enterprise-beans>
<message-driven>
<display-name>SysAlertMDB</display-name>
<ejb-name>SysAlertMDB</ejb-name>
<ejb-class>**********</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
</message-driven-destination>
<resource-ref>
<res-ref-name>jms/SysAlertTopicConnectionFactory</res-ref-name>
<res-type>javax.jms.TopicConnectionFactory</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>jms/SysAlertTopic</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
</resource-env-ref>
</message-driven>
</enterprise-beans>
</ejb-jar>
ORION-EJB.JAR
<orion-ejb-jar>
<enterprise-beans>
<message-driven-deployment max-instances="1"
name="SysAlertMDBBean"
min-instances="0"
destination-location="jms/SysAlertTopic"
connection-factory-location="jms/SysAlertTopicConnectionFactory"/>
</enterprise-beans>
</orion-ejb-jar>
JMS.XML
<topic-connection-factory name="SysAlertTopicConnectionFactory" location="jms/SysAlertTopicConnectionFactory" host="*******" port = "*******" username = "******" password = "********"/>
<topic name="SysAlertTopic" location="jms/SysAlertTopic"/>
The error:
Auto-deploying - compiling and loading...
Error deploying file:/***SysAlertMDBBean*****/ homes: No location set for Topic resource MessageDrivenBean SysAlertMDB Error in application sdr: Error loading package at file:/***SysAlertMDBBean*****/ , Error deploying file:/***SysAlertMDBBean*****/ / homes: No location set for Topic resource MessageDrivenBean SysAlertMDB
04/03/22 12:48:47 done.
04/03/22 12:48:47 Error instantiating application 'sdr' at file:/********/: Error initializing ejb-module; Exception Error in application sdr: Error loading package at file:/***SysAlertMDBBean*****/ /, Error deploying file:/***SysAlertMDBBean*****/ / homes: No location set for Topic resource MessageDrivenBean SysAlertMDB -
Getting a security exception when invoking EJB from a webservice
Hi,
I am getting the following exception when Invoke an EJB from a web service.
The EJB fails when it tries to access a remote object(RMI).
When I invoke the EJB directly I dont get this exception.
Both the EJB and the WS are deployed as part of the same application on weblogic 9.2 .
the WS was created by jwsc ant task.
This is the exception:
java.rmi.ServerException: RemoteException occurred in server thread; nested exce
ption is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested excep
tion is:
java.lang.ClassNotFoundException: com.bea.xml.XmlCalendar (no security m
anager: RMI class loader disabled)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
60)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:701)
at java.lang.Thread.run(Thread.java:534)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream
RemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
at com.netcom.server.rmi.RequestHandlerImpl_
Stub.copy(Unknown Source)
Message was edited by:
guyhHi Jitu,
I changed the wsdl. And so I don�t get the warning anymore. My Webservice also runs well, now. Thanks anyway for the reply.
There is a nice tech article on the sun network, which solved my problem. The basic idea is to split the wsdl into 2 wsdl documents. one containing all the porttypes messages and so on. And the other wsdl contains the binding and service elements.
If you are interested check out this link:
http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns/index2.html
thanks,
footman
Maybe you are looking for
-
How do I know if this variable is a file handle?
G'day (This has also been posted on StackOverflow) Say I have this code: function doFileStuff(){ var file = ""; try { file = fileOpen(filePath); // do stuff with file finally { fileClose(file); If the fileOpen() pr
-
Handling unit( 4 shirt in one pack and 8 pack in one cartoon)
hi all MM guru.... i want to the handling unit process...actually i don't have idea about this how i will start for this... actually my clint want....4 shirt packing in one packet and 8 packet in one cartoon.... then how i will manage in SAP... kin
-
Audio adjustments and P2 Workflow
I just want to make sure I'm going about things the right way before I submit a feature request for any of this. I'm starting a project that was sporadicly shot on P2 cards (DVCPRO HD 720 24p) over a couple months, I'm now going through to organize
-
Disk space allocation and FileVault
I recently had an issue with disk space in my home folder which I would like to share because it might be applicable to quite a few private (non corporate) users. The matter has been resolved, just wanted to let you know that you should be VERY CAREF
-
Impact of setting PROCTIMEOUT in icm/server_port_0
Dear Sirs, We experienced some timeout issues with internal ITS (IAC programs). The timeout happened after 60s, by note 885580 Integrated ITS: Configuration parameters and Note 705013 - Timeout for ICF services based on ITS, we identified that by inc