EJB problem under App Server 7

Hi, I get this error message when using CMP beans under app server 7. Works fine under the reference impementation but not under app server 7.
SEVERE: EJB5032: Exception in creating new bean : [{0}]
java.lang.NullPointerException
at gem.purchasing.ejb.ecx.members.EcxMembersEBEJB_1077136325_ConcreteImpl.jdoLookupPersistenceManagerFactory(Ecx
MembersEBEJB_1077136325_ConcreteImpl.java:694)
at gem.purchasing.ejb.ecx.members.EcxMembersEBEJB_1077136325_ConcreteImpl.setEntityContext(EcxMembersEBEJB_10771
36325_ConcreteImpl.java:724)
at com.sun.ejb.containers.EntityContainer$EntityContextFactory.create(EntityContainer.java:2599)
at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:176)
at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:133)
at com.sun.ejb.containers.EntityContainer.getPooledEJB(EntityContainer.java:1896)
at com.sun.ejb.containers.EntityContainer.getContext(EntityContainer.java:560)
at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:452)
at gem.purchasing.ejb.ecx.members.EcxMembersEBEJB_1077136325_ConcreteImpl_RemoteHomeImpl.create(EcxMembersEBEJB_
1077136325_ConcreteImpl_RemoteHomeImpl.java:24)
at gem.purchasing.ejb.ecx.members._EcxMembersEBHome_Stub.create(Unknown Source)
at gem.purchasing.util.ecx.EcxSupplierDefaultPopulate.create(EcxSupplierDefaultPopulate.java:189)
at gem.purchasing.util.ldapservices.DlcuPersistenceHelper.insertEcxData(DlcuPersistenceHelper.java:997)
at gem.purchasing.ejb.ldapservices.ValidatorEJB.sendToMapper(ValidatorEJB.java:981)
at gem.purchasing.ejb.ldapservices.ValidatorEJB_EJBObjectImpl.sendToMapper(ValidatorEJB_EJBObjectImpl.java:112)
at gem.purchasing.ejb.ldapservices._ValidatorEJB_EJBObjectImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:569)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:211)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:113)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:275)
at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:83)
at com.iplanet.ias.corba.ee.internal.iiop.ServicableWrapper.service(ServicableWrapper.java:25)
at com.iplanet.ias.util.threadpool.FastThreadPool$ThreadPoolThread.run(FastThreadPool.java:283)
at java.lang.Thread.run(Thread.java:536)
SEVERE: EJB5017: Exception while running preinvoke : ejbName = [EcxMembersEB]
SEVERE:
javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
java.lang.NullPointerException
at gem.purchasing.ejb.ecx.members.EcxMembersEBEJB_1077136325_ConcreteImpl.jdoLookupPersistenceManagerFactory(Ecx
MembersEBEJB_1077136325_ConcreteImpl.java:694)
at gem.purchasing.ejb.ecx.members.EcxMembersEBEJB_1077136325_ConcreteImpl.setEntityContext(EcxMembersEBEJB_10771
36325_ConcreteImpl.java:724)
at com.sun.ejb.containers.EntityContainer$EntityContextFactory.create(EntityContainer.java:2599)
at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:176)
at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:133)
at com.sun.ejb.containers.EntityContainer.getPooledEJB(EntityContainer.java:1896)
at com.sun.ejb.containers.EntityContainer.getContext(EntityContainer.java:560)
at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:452)
at gem.purchasing.ejb.ecx.members.EcxMembersEBEJB_1077136325_ConcreteImpl_RemoteHomeImpl.create(EcxMembersEBEJB_
1077136325_ConcreteImpl_RemoteHomeImpl.java:24)
at gem.purchasing.ejb.ecx.members._EcxMembersEBHome_Stub.create(Unknown Source)
at gem.purchasing.util.ecx.EcxSupplierDefaultPopulate.create(EcxSupplierDefaultPopulate.java:189)
at gem.purchasing.util.ldapservices.DlcuPersistenceHelper.insertEcxData(DlcuPersistenceHelper.java:997)
at gem.purchasing.ejb.ldapservices.ValidatorEJB.sendToMapper(ValidatorEJB.java:981)
at gem.purchasing.ejb.ldapservices.ValidatorEJB_EJBObjectImpl.sendToMapper(ValidatorEJB_EJBObjectImpl.java:112)
at gem.purchasing.ejb.ldapservices._ValidatorEJB_EJBObjectImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:569)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:211)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:113)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:275)
at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:83)
at com.iplanet.ias.corba.ee.internal.iiop.ServicableWrapper.service(ServicableWrapper.java:25)
at com.iplanet.ias.util.threadpool.FastThreadPool$ThreadPoolThread.run(FastThreadPool.java:283)
at java.lang.Thread.run(Thread.java:536)
javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
at com.sun.ejb.containers.EntityContainer$EntityContextFactory.create(EntityContainer.java:2607)
at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:176)
at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:133)
at com.sun.ejb.containers.EntityContainer.getPooledEJB(EntityContainer.java:1896)
at com.sun.ejb.containers.EntityContainer.getContext(EntityContainer.java:560)
at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:452)
at gem.purchasing.ejb.ecx.members.EcxMembersEBEJB_1077136325_ConcreteImpl_RemoteHomeImpl.create(EcxMembersEBEJB_
1077136325_ConcreteImpl_RemoteHomeImpl.java:24)
at gem.purchasing.ejb.ecx.members._EcxMembersEBHome_Stub.create(Unknown Source)
at gem.purchasing.util.ecx.EcxSupplierDefaultPopulate.create(EcxSupplierDefaultPopulate.java:189)
at gem.purchasing.util.ldapservices.DlcuPersistenceHelper.insertEcxData(DlcuPersistenceHelper.java:997)
at gem.purchasing.ejb.ldapservices.ValidatorEJB.sendToMapper(ValidatorEJB.java:981)
at gem.purchasing.ejb.ldapservices.ValidatorEJB_EJBObjectImpl.sendToMapper(ValidatorEJB_EJBObjectImpl.java:112)
at gem.purchasing.ejb.ldapservices._ValidatorEJB_EJBObjectImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:569)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:211)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:113)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:275)
INFO: CORE3282: stdout: **FROM DPH @ ecxLoad.create : java.lang.Exception: EcxSupplierDefaultPopulate calling ejb (creat
ing member): java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
INFO: CORE3282: stdout: java.rmi.RemoteException: nested exception is: java.lang.NullPointerException; nested ex
ception is:
INFO: CORE3282: stdout: java.lang.NullPointerException
Any help would be greatly appreciated.
Cheers,
Michael.

app_DLCU: There were no failed tests.
dlcuModule: There were no failed tests.

Similar Messages

Installing Access Manager under App Server platform

We have done an install of Access Manager 2005Q1 under App Server platform edition 2005Q1 (v8.1) on Linux Redhat Enterprise edition (v3).
When starting up Access Manager, we get a NoClassDefFound exception. Some postings mention some issues with the SUN mobile access, and suggest uninstalling / reinstalling, but these seem to apply to Solaris only. We have had no luck with this suggestion with Linux.
Does anyone have any other suggestions?
Thanx,
GB
[#|2005-09-14T10:50:34.118-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterpri
se.system.container.web|_ThreadID=10;|WebModule[/a
mserver]Exception starting filter amlcontroller
java.lang.NoClassDefFoundError
at com.iplanet.services.ldap.LDAPUser.getPasswd(LDAPUser.java:117)
at
com.iplanet.services.ldap.ServerInstance.getPasswd(ServerInstance.java:128)
at
com.sun.identity.security.ServerInstanceAction.run(ServerInstanceAction.java
:92)
at java.security.AccessController.doPrivileged(Native Method)
at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:210)
at
com.sun.identity.sm.ldap.SMSLdapObject.initialize(SMSLdapObject.java:143)
at
com.sun.identity.sm.ldap.SMSLdapObject.<init>(SMSLdapObject.java:118)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
sorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
torAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at com.sun.identity.sm.SMSEntry.<clinit>(SMSEntry.java:116)
at
com.sun.identity.sm.ServiceSchemaManager.<clinit>(ServiceSchemaManager.java:
67)
at
com.iplanet.am.util.AMClientDetector.getServiceSchemaManager(AMClientDetecto
r.java:219)
at
com.iplanet.am.util.AMClientDetector.<clinit>(AMClientDetector.java:94)
at com.sun.mobile.filter.AMLController.init(AMLController.java:85)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilter
Config.java:229)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFil
terConfig.java:312)
at
org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterCon
fig.java:83)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:38
81)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4528)
at com.sun.enterprise.web.WebModule.start(WebModule.java:241)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1086)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:833)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1086)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:483)
at org.apache.catalina.startup.Embedded.start(Embedded.java:894)
at com.sun.enterprise.web.WebContainer.start(WebContainer.java:707)
at
com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:507)
at
com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifec
ycle.java:54)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java
:300)
at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]

Everytime I click the Access Manager in the JES 2005Q4installer the directory server would click itself. Unchecking this prompted me for a remote repository which worked.
I wasn't able to get the install to complete with the state file, it stopped before configuring access manager.

RMI of EJB Problem Sun Application Server 8

I have an application that tries to invoke a remote ejb. If the client is on the same box as the ejb then everything works as expected. If the client makes the call from a different application server, then the errors listed below are generated CONTINIOUSLY UNTIL THE CLIENT APP SERVER IS STOPPED.
Although I specify a hostname and port of the desired server, the error in the server log displays the hostname as localhost (which is incorrect, with the correct port) :
locahhost:hostname: 127.0.0.1; port: 33702.
I know that client is communicating with the app server where the ejb reside because the other log messages show the other iiop ports of the ejb app server:
Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.0.1; port: 33702"
Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.0.1; port: 33822"
Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.0.1; port: 33922"
I use the following code to point the remote server:port:
env.put("java.naming.factory.initial", "com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url", urlString);
The value of the urlString is extracted from a properties file and
contains the server and the port information.
GENERATED ERRORS:
[#|2007-02-15T12:22:53.995-0500|WARNING|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee._DEFAULT_.rpc.transport|_ThreadID=11;|"IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.0.1; port: 33702"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2257)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2278)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:208)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:221)
at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:104)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:146)
at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:431)
at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:397)
at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at cyberCash.VerisignDriver.lookupRemoteVerisignAgentBean(VerisignDriver.java:779)
at cyberCash.VerisignDriver.createVerisignRemote(VerisignDriver.java:609)
at cyberCash.VerisignDriver.getVerisignRemote(VerisignDriver.java:579)
at cyberCash.VerisignDriver.SaveInput(VerisignDriver.java:232)
at org.apache.jsp.jsp.ePayment.verisignresults_jsp._jspService(verisignresults_jsp.java:143)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:105)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:336)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:297)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:247)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
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:585)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:189)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:371)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:264)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83)
Caused by: java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464)
at java.nio.channels.SocketChannel.open(SocketChannel.java:146)
at com.sun.corba.ee.impl.transport.DefaultSocketFactoryImpl.createSocket(DefaultSocketFactoryImpl.java:63)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:191)
... 52 more
|#]

hi
I am working with Sun java application Server 8.
I can able to create application(*.ear),
(Enterprise Java Bean) bean component,
client application
Problem is, i am unable to provide JNDI name for client application
advice needed to provide JNDI name for the client applications
i dont know whats the use of pointbase/cloudscape
(As i am new to this sjaServer 8, i need your advice)
Response to the following mail id
[email protected]
Please do the favour
thank you

Problem installing App Server 8.1 on Linux

I've got App server 8.1 that came with a Messaging Server bundle. I tried installing on a new machine, and it wouldn't go through with the full configuation at the time of install, so I took the "configure later" option.
I'm now trying to manually configure and start the App server, which usually is in /var/opt/sun/appserver/bin.
However, there's nothing in there except a PointBase directory, and there's no installer file for the appserver in /opt/sun. Anyone know where the manual installer script for the app server gets kept?

Okay - it looks like I've found the answer to my own question, unless anyone has a better answer:
http://docs.sun.com/app/docs/doc/819-2328/6n4khb8jl?a=view
This document goes over the post-install instructions for Sun Java Application server. It assumes you were able to run the installer, and then choose the "configure now" option to enter in all of the values right then and there for the install.
If you choose the "configure later" option, and don't enter in all of the server values right there, you are pretty much up a creek as I've found no way to actually do the post-install after this. There is literally no executible which does this.
The only thing I was able to do that worked was to try (and fail) to run the uninstall script, and then -- when that bombed out and wouldn't actually un-install everything, I did an rpm -qa | grep sun-, and then on EVERYTHING in that list, I did an rpm -e to remove it. That finally worked and allowed me to re-run the install.
Does anyone else have better advice on this one?
--Tad
System Administrator
Church of Scientology International
http://www.scientology-washingtondc.org

Problem reinstalling App Server 8.1 2005Q1

I installed App Server 8.1 and run it successfully. Later I had to uninstall it, but then, when I want to reinstall the App Server it fails. When I set the installation folder and press next, nothing happens.
Thanks in advance.
Marcelo.

Thanks,
it did work. I just followed the steps it mentioned and when I reinstalled the App Server 8.1 everything was successfully.
Marcelo.

Connection problems with App Server database

Hello All.
On my project it has been noticed in the database listener logs that our Application Server is attempting to make a jdbc connection to the database multiple times a second on different ports. The port numbers appear to be increasing on each attempt.
We believe this is causing the number of connections available to be rapidly taken up, and limiting the App Server from making any connections for future processes.
Here are some of the events in the database listener log:
20-AUG-2006 13:10:40 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PWTS)) * (ADDRESS=(PROTOCOL=tcp)(HOST=OUR_HOST)(PORT=37870)) * establish * PWTS * 0
20-AUG-2006 13:10:40 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PWTS)) * (ADDRESS=(PROTOCOL=tcp)(HOST=OUR_HOST)(PORT=37871)) * establish * PWTS * 0
20-AUG-2006 13:10:40 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PWTS)) * (ADDRESS=(PROTOCOL=tcp)(HOST=OUR_HOST)(PORT=37872)) * establish * PWTS * 0
20-AUG-2006 13:10:40 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PWTS)) * (ADDRESS=(PROTOCOL=tcp)(HOST=OUR_HOST)(PORT=37873)) * establish * PWTS * 0
20-AUG-2006 13:10:40 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PWTS)) * (ADDRESS=(PROTOCOL=tcp)(HOST=OUR_HOST)(PORT=37874)) * establish * PWTS * 0
20-AUG-2006 13:10:41 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PWTS)) * (ADDRESS=(PROTOCOL=tcp)(HOST=OUR_HOST)(PORT=37875)) * establish * PWTS * 0
20-AUG-2006 13:10:41 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PWTS)) * (ADDRESS=(PROTOCOL=tcp)(HOST=OUR_HOST)(PORT=37876)) * establish * PWTS * 0
Has anyone seen anything similar to this or have any suggestions as to where to look?
Thanks,
Sean

sqlnet does switch the ports dynamically, I guess for scaling and security - but I have to admit, I am not a db guru - o it's jsut what i remember from previous chats with colleaques..

Error deploying EJBs on Sun App Server

Someone please help, I am getting a strange problem when deploying an EJB jar.
I have had this code working before (before Xmas), but now I am getting the following error:
java.lang.NoSuchMethodException: com.enterprise.entity.ContentBean.getId();Remote;public abstract java.lang.Integer com.enterprise.entity.ContentRemote.getId() throws java.rmi.RemoteException;_RequestID=e1c03c30-18d9-4f08-b57f-58d97180c1d9;|EJB5111:Bean class for ejb [content:java.lang.NoSuchMethodException: com.enterprise.entity.ContentBean.getId()] does not define a method corresponding to [Remote] interface method [public abstract java.lang.Integer com.enterprise.entity.ContentRemote.getId() throws java.rmi.RemoteException]
Code snippets of offending classes:
In remote interface:
public interface ContentRemote extends EJBObject {
public Integer getId() throws RemoteException;
}In bean class:
public Integer getId() throws RemoteException {
return new Integer(this.id);
}I think the code is right, please could someone suggest where I am going wrong, this is driving me up the wall.....
Thanks.....
null

Hello,
the build runs a verifier on your EJBs and makes sure everything is in proper order. The ear file holds everything, including the jsps which are inside the war file that gets created.
Regards jP

[EJB:015001] error while deploying an ejb on weblogic app server

Hi,
I'm trying to deploy an ear which has lot of modules and it is failing for one of the ejb module. The exception is as follows:
<Mar 22, 2011 7:47:01 PM GMT+05:30> <Error> <Deployer> <WL-149265> <Failure occurred in the execution of deployment request with ID '1300803398704' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
Error processing annotations: .'
weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
Error processing annotations: .
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.utils.ErrorCollectionException:
There are 1 nested errors:
weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class trivnet.product.services.svams.ProjSVAMServiceBean in Jar D:\ccm_wa\TICP-yogesh_3.4.0\TICP\product\classes : java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1245)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:397)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1322)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
     Truncated. see log file for complete stacktrace
>
<Mar 22, 2011 7:47:01 PM GMT+05:30> <Warning> <Deployer> <WL-149004> <Failures were detected while initiating deploy task for application 'ear'.>
<Mar 22, 2011 7:47:01 PM GMT+05:30> <Warning> <Deployer> <WL-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
Error processing annotations: .
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.utils.ErrorCollectionException:
There are 1 nested errors:
weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class trivnet.product.services.svams.ProjSVAMServiceBean in Jar D:\ccm_wa\TICP-yogesh_3.4.0\TICP\product\classes : java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1245)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:397)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1322)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
     Truncated. see log file for complete stacktrace
>
There are two scenarios one of which is working and the other is not. The details are below:
Scenario 1: (Working)
There is an ejb module in the ear (say ModA) which has two session beans (SessionA and SessionB having Remote interfcaes RemoteIntA and RemoteIntB).
There is another ejb module in the ear (say ModB) which has few more session beans.
Now I want to add an ejb which will extend from SessionA.
So, I did following changes:
i. added a remote interface in ModB - RemoteIntPA implements RemoteIntA
ii. added session bean SessionPA extends SessionA implements RemoteIntPA
iii. added ejb related annotations in SessionPA and removed the annotations from SessionA (i.e., SessionA is just a normal class by itself)
Now in the application.xml I declare both modules (ModA and ModB) as ejb modules.
I deploy the application everything works fine.
Scenario 2: (Not Working)
For some reason, I didn't required SessionB in ModA (which was the only ejb bean left in that module as SessionA was converted to normal java class). So I removed SessionB and RemoteIntB.
Now as there are no ejb beans in ModA, I cannot define this as ejb module in application.xml and hence I defined it as java module.
Now if I deploy the same application, I get the exception mentioned above.
I think it has to do with the classpath issue. But how is that the classpath issue is arising when I declaring a module as java and not when I declare it as ejb. I have this module in classpath of ModB. So it doesn't matter what type of module it is.
Am I missing something?
Please help me in this regards.

java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
The JAR with the class trivnet/service/svams/SVAMService is not in the classpath.

EJB Deployment in J2EE Apps Server

Hi,
Can any one please help me in deploying EJB in J2EE Apps server?I have installed J2EE Apps Server 9 in my machine.Can any one please suggest me a document regarding EJB deployment in J2EE apps server or help me regarding this?
Thanks in advance,
Aravindhan.C

Go to https://j2ee-sdk.dev.java.net/ and checkout "Methods of deploying applications" under the recent articles section; The tutorial link present in this page (under the references section) will also be useful. The samples bundle has reference samples which will also be useful

Deployement problem in Oracle App Serv with hibernate + JPA and Spring

Dear All,
     I am facing a problem in deployment of a web application in oracle application server 10g. but the same is working fine with Tomcat. The following Exception. Is being thrown.
     Failed to deploy web application "OraTest". Failed to deploy web application OraTest". . Nested exception Resolution:
Base Exception:
java.rmi.RemoteException
deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: version. deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: version     I am using the following technologies
1.     Spring 2.0.7
2.     Struts 2.0.9
3.     Hibernate 3.3
4.     JPA 1.0
5.     Oracle App Server 10.1.2.0.2
Web.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
     <display-name>My Application</display-name>
     <filter>
          <filter-name>struts2</filter-name>
          <filter-class>
               org.apache.struts2.dispatcher.FilterDispatcher
          </filter-class>
     </filter>
     <filter-mapping>
          <filter-name>struts2</filter-name>
          <url-pattern>/*</url-pattern>
     </filter-mapping>
     <welcome-file-list>
          <welcome-file>/index.jsp</welcome-file>
     </welcome-file-list>
     <servlet>
          <servlet-name>dwr-invoker</servlet-name>
          <servlet-class>
               org.directwebremoting.servlet.DwrServlet
          </servlet-class>
          <init-param>
               <param-name>debug</param-name>
               <param-value>true</param-value>
          </init-param>
     </servlet>
     <servlet-mapping>
          <servlet-name>dwr-invoker</servlet-name>
          <url-pattern>/dwr/*</url-pattern>
     </servlet-mapping>
     <listener>
          <listener-class>
               org.springframework.web.context.ContextLoaderListener
          </listener-class>
     </listener>
     <context-param>
          <param-name>contextConfigLocation</param-name>
          <param-value>
               /WEB-INF/conf/spring/datasource-context.xml,
               /WEB-INF/conf/spring/aop-context.xml
          </param-value>
     </context-param>
</web-app>
/Datasource-context.xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd">
     <bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor" lazy-init="true"/>
     
        <bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource" lazy-init="true">
          <property name="driverClassName">
               <value>oracle.jdbc.driver.OracleDriver</value>
          </property>
          <property name="url">
               <value>jdbc:oracle:thin:@//xxx.xxx.xxx.xxx/mydb</value>
          </property>
          <property name="username">
               <value>admin</value>
          </property>
          <property name="password">
               <value>admin</value>
          </property>
     </bean>
     
     
     <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean" lazy-init="true">
          <property name="persistenceUnitName" value="mkclsetsPersistenceUnit"/>
          <property name="dataSource" ref="dataSource"/>
          <property name="jpaVendorAdapter">
               <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter" lazy-init="true">
                    <property name="database" value="ORACLE"/>
                    <property name="showSql" value="true"/>
               </bean>
          </property>
     </bean>
     <bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager" lazy-init="true">
          <property name="entityManagerFactory" ref="entityManagerFactory"></property>
     </bean>
     <tx:annotation-driven transaction-manager="transactionManager"/>
</beans>Aop-context.xml
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd">

     <bean id="methodLoggingAdvice" class="com.mkcl.sets.common.interceptor.MehodLogInterceptor"/>
     
      
     <bean id="methodCachingAdvice"
          class="com.mkcl.sets.common.interceptor.MethodCacheInterceptor">
          <property name="cache">
               <ref local="methodCache" />
          </property>
     </bean>
     <bean id="cacheManager"
          class="org.springframework.cache.ehcache.EhCacheManagerFactoryBean">
          <property name="configLocation">
               <value>WEB-INF/conf/other/ehcache.xml</value>
          </property>
     </bean>
     <bean id="methodCache"
          class="org.springframework.cache.ehcache.EhCacheFactoryBean">
          <property name="cacheManager">
               <ref local="cacheManager" />
          </property>
          <property name="cacheName">
               <value>mkclSetsCache</value>
          </property>
     </bean>
     
     <aop:config>
          <aop:pointcut id="getCountriesPointCut" expression="execution(* com.mkcl.sets.dao.master.impl.LocationDAOImpl.getCountries())"/>
          
          <aop:pointcut id="methodLogPointCutDao" expression="execution(* com.mkcl.sets.dao..*.*(..))"/>
          <aop:pointcut id="methodLogPointCutService" expression="execution(* com.mkcl.sets.service..*.*(..))"/>
          <aop:advisor id="methodCachingAdvisor" advice-ref="methodCachingAdvice" pointcut-ref="getCountriesPointCut"/>
          <aop:advisor id="methodLoggingAdvisorDao" advice-ref="methodLoggingAdvice" pointcut-ref="methodLogPointCutDao"/>
          <aop:advisor id="methodLoggingAdvisorService" advice-ref="methodLoggingAdvice" pointcut-ref="methodLogPointCutService"/>
     </aop:config>
</beans>Persistence.xml
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
    version="1.0">
     <persistence-unit name="mkclsetsPersistenceUnit" transaction-type="RESOURCE_LOCAL">
          
          <provider>org.hibernate.ejb.HibernatePersistence</provider>
          
     </persistence-unit>
</persistence>Do I need to add some other configuration in the existing files or do I need to add some other configuration files ? Please help to deploy my application.
Thanks a lot in advance.
With Best Regards,
Ishaan
null

Did you ever find a solution to this Ishaan?
I imagine you ended up having to upgrade 10gR2 to 10gR3 at least. Correct?

Problems between IDE and Deployment on App Server 8.2

I have an application that I wrote last year using JSC-EA and converted it ti JSC2-1. I can run the application on my development environment SunAppServer 8.2 with no problems.
When I attempt to deploy it to a standalone Sun App Server 8.2 I experience the following:
1) Login page works fine
2) Main menu selection page works fine
3) Results page does not display information.
More details:
Main Menu page consists of:
1) a page with a page fragment that contains a menu.
2) 3 or 4 JSF components
Results page consists of:
1) 2-3 JSF text components (display OK)
2) Same menu page fragment as above (displays OK)
3) Second page fragment that contains a table with components added under program control (does not get displayed in deployment server, but displays fine in IDE server).
Is there ANY possibility that this can be related to migration from JSC2-EA to JSC2-1? If so, what could cause this behavior?
Is there ANY explanation as to why the application displays OK in the IDE (same app server version as deployment) but not in the deployment server?
ANY help is appreciated.
Thanks,

For future references:
this happens to me too and I found that the cause is that the AM server you are going to configure, is already registered into the directory server.
Try running this command (with the obvious parameters substituted)
ldapsearch -B -T -D 'cn=directory manager' -w YOUR_CREDENTIALS -b ou=1.0,ou=iPlanetAMPlatformService,ou=services,YOUR_BASEDN -s base objectclass=* | grep YOUR_SERVERNAMEIf you found that the server you are configuring is listed here try going to AMserver console (if you have another AMserver configured) and browse to Configuration->System Properties->Platforms. If the server is here, remove it, if not, just hit Save (very important).
If this is your first AM and is a first installation you can just get rid of the Directory Server suffix and recreate it with the Top Entry alone.
Edited by: flistello on Mar 27, 2008 4:30 PM

NB & Sun One App Server 8.0 Bundle Admin User/Password & 503 Problem,

Hi,
Do you know the the username and password to enter admin console in Netbeans 3.6 & Sun One App Server 8.0 Bundle?
Also when I executed my first app with the software, I got this message "HTTP Status 503 - This application is not currently available". Can you tell me what is this problem and how to fix it.
Thanks very much,
Blessings,
Lorenzo Jimenez

Hi,
Do you see the deployed web application either in the admin console on in the runtime tab explorer of NetBeans, under the
Sun Java System Application Server 8 --->Applications--->Web Applications
node?
503 error is a Service unavailable error:
"The server is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. "
Can you try to reload the page for this web app?
Ludo

Sun App Server 9.0_01 (build b14) Deployment (undeploy) problems

Hi all,
I apologize for this long post but I want to provide as much info as possible. Also, I am not sure this is the right place for this posting. I will appreciate it if anyone could direct me to a better place.
I have this ongoing problem deploying my application. The app server is unable to completely delete the previously deployed files. It goes into a series of timeout loops saying it is running the gc to try and free up resources. The files that can't be deleted are all in the web application's lib folder. I tried deleting them manually while waiting for the app server timeout loop and indeed each one is busy and can't be deleted. None of the files here are my code. The files are all in the folder:
domain1\applications\j2ee-apps\TS5529\U04A1_war\WEB-INF\lib
and the files are: appbase.jar, commons-fileupload.jar, dataprovider.jar, errorhandler.jar, jsfcl.jar, json2.jar, rowset.jar, sqlx.jar, webui-jsf.jar, webui-jsf-suntheme.jar
I have made sure destroy() method in my SessionBean nulls out any resources used, even variables containing injected EJBs but the problem remains.
The application is a NetBeans Enterprise application with a couple of Session Beans, Entity classes and Entity Facades. The presentation is JSF with Visual Web Pack and consists of two simple pages. The SessionBean holds a reference to a Stateful Bean and 4 variables each containing a custom ListDataProvider for JSF tables data binding. The SessionBean destroy method sets all of these variables to null.
The first page backing bean does most of the work. It accesses the SFSB and DataProviders through the SessionBean. This page includes four EJB injections like this:
@EJB AuthorFacadeLocal af;
@EJB PublisherFacadeLocal pf;
@EJB SearchDBLocal sDB;
@EJB TitleFacadeLocal tf;
and a variable holding an empty, unmanaged Entity object. I tried setting all of these to null in the page's destroy() method, which I don;t think I need to do.
Is there a problem with these injections in the page's backing bean?? I've been at this for about a week, trying various ways to make sure resources are freed but the problem still there. The only solution is to stop the app server and then deploy. Needless to say, it is a pain having to stop the app server every time I need to deploy.
Hope someone has seen this and can help, thanks in advance.

Hi all,
I apologize for this long post but I want to provide as much info as possible. Also, I am not sure this is the right place for this posting. I will appreciate it if anyone could direct me to a better place.
I have this ongoing problem deploying my application. The app server is unable to completely delete the previously deployed files. It goes into a series of timeout loops saying it is running the gc to try and free up resources. The files that can't be deleted are all in the web application's lib folder. I tried deleting them manually while waiting for the app server timeout loop and indeed each one is busy and can't be deleted. None of the files here are my code. The files are all in the folder:
domain1\applications\j2ee-apps\TS5529\U04A1_war\WEB-INF\lib
and the files are: appbase.jar, commons-fileupload.jar, dataprovider.jar, errorhandler.jar, jsfcl.jar, json2.jar, rowset.jar, sqlx.jar, webui-jsf.jar, webui-jsf-suntheme.jar
I have made sure destroy() method in my SessionBean nulls out any resources used, even variables containing injected EJBs but the problem remains.
The application is a NetBeans Enterprise application with a couple of Session Beans, Entity classes and Entity Facades. The presentation is JSF with Visual Web Pack and consists of two simple pages. The SessionBean holds a reference to a Stateful Bean and 4 variables each containing a custom ListDataProvider for JSF tables data binding. The SessionBean destroy method sets all of these variables to null.
The first page backing bean does most of the work. It accesses the SFSB and DataProviders through the SessionBean. This page includes four EJB injections like this:
@EJB AuthorFacadeLocal af;
@EJB PublisherFacadeLocal pf;
@EJB SearchDBLocal sDB;
@EJB TitleFacadeLocal tf;
and a variable holding an empty, unmanaged Entity object. I tried setting all of these to null in the page's destroy() method, which I don;t think I need to do.
Is there a problem with these injections in the page's backing bean?? I've been at this for about a week, trying various ways to make sure resources are freed but the problem still there. The only solution is to stop the app server and then deploy. Needless to say, it is a pain having to stop the app server every time I need to deploy.
Hope someone has seen this and can help, thanks in advance.

EJB not getting bound to JNDI name using Sun App Server upon deployment

Hello,
I've created a very simple "HelloWorld" EJB (2.1-style) and have successfully deployed it to my local application server (Sun Java System App Server Platform Edition 9.0). I now want to invoke the EJB (I have single stateless session bean that returns a string) using a simple remote client app (the client app is executing outside of the app server within its own JVM).
From my client app I am able to create the InitialContext object, but I get error when trying to lookup my EJB's home object. My client looks as follows:
               jndiProperties = new Properties();
               jndiProperties.put("java.naming.factory.initial",
                    "com.sun.jndi.cosnaming.CNCtxFactory");
               jndiProperties.put("java.naming.provider.url",
                    "iiop://localhost:3700"); // ORB listener is listening on port 3700...
               context = new InitialContext(jndiProperties);
               home = context.lookup("ejb/HelloWorldEJB"); // this line throws an exception (line 54)
               ...The exception I receive is:
               [java] 234 ERROR [main] net.blueslate.sample.ejb.helloworld.HelloWorldClient     - javax.namin
g.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.
org/CosNaming/NamingContext/NotFound:1.0]
     [java]     at com.sun.jndi.cosnaming.ExceptionMapper.mapException(ExceptionMapper.java:44)
     [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:453)
     [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
     [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
     [java]     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     [java]     at net.blueslate.sample.ejb.helloworld.HelloWorldClient.main(HelloWorldClient.java:5
4)
     [java] Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/Naming
Context/NotFound:1.0
     [java]     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72
     [java]     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
     [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
     [java]     ... 4 moreHere is my ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar
     xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
     version="2.1">
     <enterprise-beans>
          <session>
               <ejb-name>HelloWorldEJB</ejb-name>
               <home>net.blueslate.sample.ejb.helloworld.HelloWorldRemoteHome</home>
               <remote>net.blueslate.sample.ejb.helloworld.HelloWorldRemote</remote>
               <local-home>net.blueslate.sample.ejb.helloworld.HelloWorldLocalHome</local-home>
               <local>net.blueslate.sample.ejb.helloworld.HelloWorldLocal</local>
               <ejb-class>net.blueslate.sample.ejb.helloworld.impl.HelloWorldImpl</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
          </session>
     </enterprise-beans>
</ejb-jar>Here is my sun-ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
<sun-ejb-jar>
     <enterprise-beans>
          <ejb>
               <ejb-name>HelloWorldEJB</ejb-name>
               <jndi-name>HelloWorldEJB</jndi-name>
          </ejb>
     </enterprise-beans>
</sun-ejb-jar>I believe the root cause is that my EJB is not bound to a name within the app server. If I browse the "JNDI tree" from the app server admin console, I can see there is a root element "ejb," but there is nothing underneath. I guess I just expected to find the name of my EJB, "HelloWorldEJB." I swear I could have read somewhere in the documentation for the app server that when you deploy an EJB, the name of the EJB as specified by the "<ejb-name>" element of the ejb-jar.xml deployment descriptor gets automatically bound within the naming server to its home object.
At this point I would appreciate any insight anyone might have regarding this problem. I suspect there is something extra I need to do when deploying my EJB so that its name gets binded to its home object; I just don't have a clue at this point what that is.
I should also mention that I have played with the parameter passed to 'context.lookup()' - I tried passing: "ejb/HelloWorldEJB", "HelloWorldEJB", etc - nothing seems to work. FWIW, if I just pass in "ejb", I don't receive an exception (I was glad to see this work since the JNDI tree-view from the app server admin console shows "ejb" as one of the root-elements within the naming-tree - this indicated to me I was on the right track in my diagnosis of the problem; i.e., it's probably not a connectivity or protocol issue)
Thank you very much for your time and help.

Nevermind folks - I got it to work. All my configuration was correct; I had other issues with the ejb-jar file that the verifier informed me of (my previous deployments were with the verifier turned-off).

Distributed transactions, EJB and Sun Java App Server

Hello,
I'm trying to implement a CMT Stateless EJB that inserts data into a Oracle 9.2 table. All this running into a Sun Java System App Server 8.2 and using a XA Database Connection Pool.
Before starting bothering you, a simple question: has anybody successfully retrieved a connection from a XA connection pool? I've read somewhere that Oracle thin client is very limited and I wonder if one of its limitations would be "no support to XA transactions".
My pool information:
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="oracle.jdbc.xa.client.OracleXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" max-pool-size="32" max-wait-time-in-millis="60000" name="MyXAPool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8" transaction-isolation-level="read-committed">
<property name="DataSourceName" value="OracleXADataSource"/>
<property name="ImplicitCachingEnabled" value="false"/>
<property name="NetworkProtocol" value="tcp"/>
<property name="LoginTimeout" value="0"/>
<property name="Password" value="arbor123"/>
<property name="URL" value="jdbc:oracle:thin:@HostName:1521:Alias"/>
<property name="NativeXA" value="false"/>
<property name="User" value="arbor"/>
<property name="ExplicitCachingEnabled" value="false"/>
</jdbc-connection-pool>
I created a jdbc resource called jdbc/__myxa so I can access the database pool using JNDI.
The code:
InitialContext jndiContext = new InitialContext();
DataSource ds = (DataSource) jndiContext.lookup("jdbc/__myxa");
Connection con = ds.getConnection();
PreparedStatement ps = con.prepareStatement( "INSERT INTO TESTE_CLAUDIO( MSG, MSG_DT) VALUES ('" + aMessage + "', SYSDATE)" );
ps.execute();
con.close();
When attempting to get the connection, I got an exception saying that:
"This Managed Connection is not valid as the phyiscal connection is not usable"
Thanks for any information

Hi Claudio,
J2EE applications should retrieve all their resources through their component environment (java:comp/env) -- not by doing a global JNDI lookup. You should declare a resource-ref in ejb-jar.xml for the bean and then map that resource-ref to your physical data source (jdbc/__myxa) in sun-ejb-jar.xml. E.g, if the res-ref-name is "foo", your code would look it up under context.lookup("java:comp/env/foo");
--ken

EJB problem under App Server 7

Similar Messages

Maybe you are looking for