WAS 6.0 Deployment problem

[YuenLian Wu]

When I was trying to deploy an EJB project to WAS 6.0 server, the project was started without any exception message, but its listener ports were stopped automatically.

I got following logs:

[1/10/07 10:25:07:244 GMT+08:00] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[1/10/07 10:25:09:073 GMT+08:00] 0000000a AdminInitiali A ADMN0015I: The administration service is initialized.
[1/10/07 10:25:10:519 GMT+08:00] 0000000a SystemOut O PLGC0057I: Plug-in configuration service is started successfully.
[1/10/07 10:25:10:596 GMT+08:00] 0000000a PMIImpl A PMON1001I: PMI is enabled
[1/10/07 10:25:11:893 GMT+08:00] 0000000a SibMessage I [:] CWSIU0000I: Release: WAS602.SIB Level: o0613.11
[1/10/07 10:25:11:918 GMT+08:00] 0000000a SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.c
ore.SecurityDM registered successfully: true.
[1/10/07 10:25:11:985 GMT+08:00] 0000000a AuditServiceI A SECJ6004I: Security Auditing is disabled.
:1652
[1/10/07 18:44:56:473 GMT+08:00] 0000000a WebContainer A SRVE0239I: Extension Factory [class com.ibm.ws.jsf.extprocessor.JSFExtensionFact
ory] was registered successfully.
[1/10/07 18:44:56:477 GMT+08:00] 0000000a WebContainer A SRVE0240I: Extension Factory [class com.ibm.ws.jsf.extprocessor.JSFExtensionFact
ory] has been associated with patterns [""].
[1/10/07 18:44:56:577 GMT+08:00] 0000000a ApplicationMg A WSVR0200I: Starting application: UTYAPP_App
[1/10/07 18:44:57:056 GMT+08:00] 0000000a EJBContainerI I WSVR0207I: Preparing to start EJB jar: UOETRYServiceEJB.jar
[1/10/07 18:44:57:094 GMT+08:00] 0000000a EJBContainerI I WSVR0037I: Starting EJB jar: UOETRYServiceEJB.jar
[1/10/07 18:44:57:725 GMT+08:00] 0000000a ConnectionFac I J2CA0107I: Component-managed authentication alias not specified for connection f
actory or datasource JMS$UTRY App Connection Factory.
[1/10/07 18:44:57:971 GMT+08:00] 0000000a MDBListenerIm I WMSG0043I: MDB Listener UTYAPP_UOEWEB_ListenerPort stopped for JMSDestination jm
s/utyapp_from_utyweb_req_01
[1/10/07 18:44:57:986 GMT+08:00] 0000000a MDBListenerIm I WMSG0058I: Listener Port UTYAPP_UOEWEB_ListenerPort will attempt to restart in 6
0 seconds
[1/10/07 18:44:58:009 GMT+08:00] 0000000a ApplicationMg E WSVR0101W: An error occurred starting, UTYAPP_App
[1/10/07 18:44:58:013 GMT+08:00] 0000000a ApplicationMg A WSVR0217I: Stopping application: UTYAPP_App
[1/10/07 18:44:58:022 GMT+08:00] 0000000a MDBListenerIm I WMSG0043I: MDB Listener UTYAPP_UOEWEB_ListenerPort stopped for JMSDestination jm
s/utyapp_from_utyweb_req_01
[1/10/07 18:44:58:053 GMT+08:00] 0000000a EJBContainerI I WSVR0041I: Stopping EJB jar: UOETRYServiceEJB.jar
[1/10/07 18:44:58:119 GMT+08:00] 0000000a MDBListenerIm I WMSG0043I: MDB Listener UTYAPP_UOEWEB_ListenerPort stopped for JMSDestination jm
s/utyapp_from_utyweb_req_01
[1/10/07 18:44:58:123 GMT+08:00] 0000000a MDBListenerIm I WMSG0043I: MDB Listener UTYAPP_UOEWEB_ListenerPort stopped for JMSDestination jm
s/utyapp_from_utyweb_req_01
[1/10/07 18:44:58:182 GMT+08:00] 0000000a ApplicationMg A WSVR0220I: Application stopped: UTYAPP_App
[1/10/07 18:44:58:347 GMT+08:00] 0000000a TCPChannel A TCPC0001I: TCP Channel TCP_2 is listening on host * (IPv6) port 16068.
[1/10/07 18:44:58:396 GMT+08:00] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain WCInbound.
[1/10/07 18:44:58:427 GMT+08:00] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain SOAPAcceptorChain1.
[1/10/07 18:44:58:466 GMT+08:00] 0000004c SchedulerServ I SCHD0077I: The Scheduler Service is starting the Schedulers.
[1/10/07 18:44:58:544 GMT+08:00] 0000000a RMIConnectorC A ADMC0026I: The RMI Connector is available at port 16063
[1/10/07 18:44:58:563 GMT+08:00] 0000004c SchedulerServ I SCHD0078I: The Scheduler Service has completed starting the Schedulers.
[1/10/07 18:44:58:644 GMT+08:00] 00000014 WorkSpaceMana A WKSP0500I Workspace configuration consistency check is false.
[1/10/07 18:45:01:164 GMT+08:00] 00000014 SystemOut O dumping EngineParameters
[1/10/07 18:45:01:164 GMT+08:00] 00000014 SystemOut O enabled=false
[1/10/07 18:45:01:164 GMT+08:00] 00000014 SystemOut O traceResponseEnabled=true
[1/10/07 18:45:01:164 GMT+08:00] 00000014 SystemOut O traceResponseLevel=104
[1/10/07 18:45:01:164 GMT+08:00] 00000014 SystemOut O fileResponseEnabled=false
[1/10/07 18:45:01:164 GMT+08:00] 00000014 SystemOut O fileResponseLevel=108
[1/10/07 18:45:01:165 GMT+08:00] 00000014 SystemOut O mBeanResponseEnabled=false
[1/10/07 18:45:01:165 GMT+08:00] 00000014 SystemOut O mBeanResponseLevel=108


Does anyone know what is the problem? Any possible thing will make this occured? Thanks!!!

[Cameron Wallace McKenzie]

It looks to me like a JAAS authentication alias has not been set up for the data source your EJBs use. As a result, when your entity beans start up, they cannot find the authentication alias, and as a result, they can't connect to the database. Then all heck breaks loose.

Set up an authentication alias with the name/password to connect to the database. Then associate the datasource with this authentication alias. See if that works.

If your sever is running, do a namespace dump using the dumpnamespace utility and see if the datasource is indeed bound to the JNDI naming service.

I believe there is a point in the following tutorial where I do exactly that when I deploy an entity bean heavy application to WebSphere. I even think it's version 5 for you:

Multimedia Tutorial on Deploying EJBs, MDBs, Entity Beans and Web Applications (a complex EAR) to WebSphere 5

Happy WebSphere!

-Cameron McKenzie