Author |
Message
|
CHF |
Posted: Tue Dec 21, 2004 12:15 pm Post subject: WAS 5.1.0 Startup errors - MDB not picking up messages |
|
|
 Master
Joined: 16 Dec 2003 Posts: 297
|
We are running WAS 5.1.0 on mainframes. We have MDB in one of the project's.
The MDB is not picking up the messages from the queue. Here is the server log... can anyone please let me what's the problem...
This is my environment,
************ Start Display Current Environment ************
WebSphere Platform 5.1 [BASE 5.1.0 W510004] [ND 5.1.0 W510004] running with process name cell1l\node1\SERVER1 and process id XXBCXXX05BE96XXX37D30746000003A40000000CB0591301
Host Operating System is z/OS, version 01.04.00
Java version = J2RE 1.4.2 IBM z/OS Persistent Reusable VM build cm142-20040917 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = /Waso3/AppServer
user.install.root = /Waso3/AppServer
Java Home = /usr/lpp/java14/J1.4
ws.ext.dirs = /usr/lpp/java14/J1.4/lib:/Waso3/AppServer/classes:/Waso3/AppServer/lib:/Waso3/AppServer/lib/ext:/Waso3/AppServer:/Waso3/AppServer/web/help:/Waso3/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = /Waso3/AppServer/properties:/Waso3/AppServer/lib/bootstrap.jar:/Waso3/AppServer/lib/urlprotocols.jar:/Waso3/AppServer/lib/j2ee.jar:/Waso3/AppServer/lib/lmproxy.jar:/usr/lpp/wmqwtst/bin/java3402/fmcojagt.jar
Java Library path = /usr/lpp/java14/J1.4/bin:/usr/lpp/java14/J1.4/bin/classic:/Waso3/AppServer/lib:/usr/lpp/wmqwtst:/usr/lpp/wmqmtst/java/lib
************* End Display Current Environment *************
Server log
[12/17/04 21:14:11:676 GMT+00:00] 1359a920 ApplicationMg A WSVR0200I: Starting application: SampleEAR
[12/17/04 21:14:14:064 GMT+00:00] 1359a920 EJBContainerI I WSVR0207I: Preparing to start EJB jar: SampleEJB.jar
[12/17/04 21:14:16:735 GMT+00:00] 1359a920 EJBContainerI I WSVR0037I: Starting EJB jar: SampleEJB.jar
[12/17/04 21:14:18:379 GMT+00:00] 548fa92d WebContainer A SRVE0169I: Loading Web Module: SampleWeb.
[12/17/04 21:14:20:475 GMT+00:00] 548fa92d TraceNLS u No message text associated with key getTempDirectory:.using./Waso3/AppServer.as.server.root in bundle com.ibm.ejs.resources.seriousMessages
[12/17/04 21:14:20:475 GMT+00:00] 548fa92d WebGroup W getTempDirectory: using /Waso3/AppServer as server.root
[12/17/04 21:14:20:572 GMT+00:00] 548fa92d WebGroup I SRVE0180I: [SampleWeb] [/SampleWeb] [Servlet.LOG]: JSP 1.2 Processor: init
[12/17/04 21:14:22:765 GMT+00:00] 548fa92d WebGroup I SRVE0180I: [SampleWeb] [/SampleWeb] [Servlet.LOG]: SimpleFileServlet: init
[12/17/04 21:14:22:838 GMT+00:00] 548fa92d WebGroup I SRVE0180I: [SampleWeb] [/SampleWeb] [Servlet.LOG]: InvokerServlet: init
[12/17/04 21:14:23:074 GMT+00:00] 548fa92d WebGroup I SRVE0180I: [SampleWeb] [/SampleWeb] [Servlet.LOG]: action: init
[12/17/04 21:14:23:229 GMT+00:00] 548fa92d PropertyMessa I org.apache.struts.util.PropertyMessageResources Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true
[12/17/04 21:14:23:235 GMT+00:00] 548fa92d PropertyMessa I org.apache.struts.util.PropertyMessageResources Initializing, config='org.apache.struts.action.ActionResources', returnNull=true
[12/17/04 21:14:25:735 GMT+00:00] 548fa92d PropertyMessa I org.apache.struts.util.PropertyMessageResources Initializing, config='com.chase.chf.Sampleweb.resources.ApplicationResources', returnNull=true
[12/17/04 21:14:28:996 GMT+00:00] 1359a920 ApplicationMg A WSVR0221I: Application started: SampleEAR
[12/17/04 21:14:29:165 GMT+00:00] 1359a920 HttpTransport A SRVE0171I: Transport http is listening on port 9,080.
[12/17/04 21:14:29:176 GMT+00:00] 1359a920 HttpTransport A SRVE0171I: Transport https is listening on port 9,443.
[12/17/04 21:14:29:187 GMT+00:00] 1359a920 ContainerImpl E WSVR0501E: Error creating component null [class com.ibm.ws.runtime.component.ApplicationServerImpl]
com.ibm.ws.exception.RuntimeWarning
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:885)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResource(ResourceMgrImpl.java:801)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(ResourceMgrImpl.java:747)
at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(ResourceMgrImpl.java:589)
at com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrImpl.java:501)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:125)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:239)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:148)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:248)
at com.ibm.ws390.orb.CommonBridge.WsServerStartup(CommonBridge.java:371)
at com.ibm.ws390.orb.ServerRegionBridge.initCSI(ServerRegionBridge.java:196)
at com.ibm.ws390.orb.ORBEJSBridge.initCSI(ORBEJSBridge.java:166)
Caused by: com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid configuration passed to resource binding logic. REASON: java.lang.NullPointerException
at com.ibm.ws.runtime.component.binder.WASQueueConnectionFactoryBinder.getBindingObject(WASQueueConnectionFactoryBinder.java:193)
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImpl.java:297)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:876)
... 15 more
---- Begin backtrace for nested exception
com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid configuration passed to resource binding logic. REASON: java.lang.NullPointerException
at com.ibm.ws.runtime.component.binder.WASQueueConnectionFactoryBinder.getBindingObject(WASQueueConnectionFactoryBinder.java:193)
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImpl.java:297)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:876)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResource(ResourceMgrImpl.java:801)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(ResourceMgrImpl.java:747)
at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(ResourceMgrImpl.java:589)
at com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrImpl.java:501)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:125)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:239)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:148)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:248)
at com.ibm.ws390.orb.CommonBridge.WsServerStartup(CommonBridge.java:371)
at com.ibm.ws390.orb.ServerRegionBridge.initCSI(ServerRegionBridge.java:196)
at com.ibm.ws390.orb.ORBEJSBridge.initCSI(ORBEJSBridge.java:166)
[12/17/04 21:14:31:923 GMT+00:00] 1359a920 WsServer A WSVR0002I: Server SERVANT PROCESS SERVER1 open for e-business, problems occurred during startup
Thanks in Advance _________________ CHF  |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Dec 21, 2004 1:44 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
CHF wrote: |
Caused by: com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid configuration passed to resource binding logic. REASON: java.lang.NullPointerException
at com.ibm.ws.runtime.component.binder.WASQueueConnectionFactoryBinder.getBindingObject(WASQueueConnectionFactoryBinder.java:193)
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImpl.java:297)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:876)
... 15 more
---- Begin backtrace for nested exception
com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid configuration passed to resource binding logic. REASON: java.lang.NullPointerException
at com.ibm.ws.runtime.component.binder.WASQueueConnectionFactoryBinder.getBindingObject(WASQueueConnectionFactoryBinder.java:193)
|
I believe the error message is pretty clear.
You need to check your resource definitions. If you are using IBM WAS check the setup of JMS MQ Provider. Remember java IS CASE SENSITIVE
Make sure all the classpath needs are satisfied.
Enjoy  |
|
Back to top |
|
 |
CHF |
Posted: Tue Dec 21, 2004 2:02 pm Post subject: |
|
|
 Master
Joined: 16 Dec 2003 Posts: 297
|
fjb_saper:
Thanks for the reply.
I have double checked the resource definitions and they are correct. Forgot to tell last time that if I use a different WAS 5.1.0 that is on a Windows test Box and define the resources WebSphere MQ Queue Connection Factories (Transport Type = Client) & WebSphere MQ Queue Destinations to pick the messages from the Queue on Mainframe, it works absolutely fine. With that I am guessing may be I do not have some Fix Packs applied onto WAS 5.1.0 on mainframe. What do you think?
Thanks again _________________ CHF  |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Dec 21, 2004 6:30 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
what is the version of WAS and version of MQ.? (major + minor)
When we went to CSD06 we had to apply some fix paks to WAS.
Check with IBM what fixes for WAS you need.
We are at MQ 5.3.08 (CSD08) right now and have not needed to patch WAS (5.x)since we did it at CSD06. Our platform is AIX.
Enjoy  |
|
Back to top |
|
 |
CHF |
Posted: Thu Dec 23, 2004 5:48 am Post subject: |
|
|
 Master
Joined: 16 Dec 2003 Posts: 297
|
WAS 5.1.0 (No fix packs)
MQ - 5.3 (Don't know about Fix packs).
As i mentioned earlier I feel like its the fixpacks problem. Contacting IBM regarding this. Anyways, thatnks for your time Saper. _________________ CHF  |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Dec 23, 2004 11:05 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
for MQ Version display on Unix with CSD :
mqver -- server version
dspmqver == client version
Make sure as well that you have the XA checkbox checked on your QCF definition if you plan to do 2 phase commit.... and that the MQ server is on the same machine as WAS...
Enjoy  |
|
Back to top |
|
 |
|