Standalone JMS Client problem hetting the connection - Please Advice
xg...@yahoo.com
I am wracking my brain for the past 2 days to figure out how to fix this error. I googled and looked into the forum but all efforts were in vain.
I am trying to run standalone JMS Client to put the message into the queue.
Environment - RAD 6.0
Configuration
----------------
JMS Providers -> Default Messaging -> Configured Connection Factory and associated with the BUS.
JMS Providers -> Default Messaging -> Configured Queue
Service Integration -> Bus -> Configured a Bus
Buses > mybus > Bus members > Messaging engines - Started
Now, configuration is done.
My client program
--------------------
private void putMessage()
{
try
{
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://localhost:2809");
Context initialContext = new InitialContext(env);
ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("myconnectionfactory");
Queue queue = (Queue)initialContext.lookup("myqueue");
Connection conn = connectionFactory.createConnection();
conn.start();
Session session = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
...
...
...
conn.stop();
}
catch(Exception e)
{
// oooooooopss somethign wrong
}
}
It is erroring at Connection conn = connectionFactory.createConnection();
Below is the stack trace
----------------------------
ep 27, 2006 11:40:03 AM com.ibm.ws.sib.utils.ras.SibMessage
SEVERE: SIB_MESSAGE
Sep 27, 2006 11:40:03 AM com.ibm.ws.sib.utils.ras.SibMessage
WARNING: SIB_MESSAGE
javax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to contact a messaging engine in bus mybus..
at com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:225)
at com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:148)
at JMSTest.getContext(JMSTest.java:122)
at JMSTest.main(JMSTest.java:165)
Caused by: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to contact a messaging engine in bus mybus.
at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl2.remoteBootstrap(TrmSICoreConnectionFactoryImpl2.java:374)
at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl2.createConnection(TrmSICoreConnectionFactoryImpl2.java:147)
at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl2.createConnection(TrmSICoreConnectionFactoryImpl2.java:95)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.createCoreConnection(JmsJcaConnectionFactoryImpl.java:498)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.createCoreConnection(JmsJcaConnectionFactoryImpl.java:434)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.createConnection(JmsJcaConnectionFactoryImpl.java:277)
at com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:195)
I really will appreciate if someone could help.
Stephen Cocks
you configured via the console?
If not it will be looking to connect to localhost:7276 to bootstrap
connection to the bus (which might not be appropriate in your environment)
--
Stephen Cocks
WESB/WPS System Administration
<xg...@yahoo.com> wrote in message
news:876711375.1159373246...@ltsgwas010.sby.ibm.com...
xg...@yahoo.com
[167.230.98.52]:7276:BootstrapBasicMessaging. (As per the document).
I have doubt over my client code, I hope code for getting the context is correct.
> env.put(Context.PROVIDER_URL, "iiop://localhost:2809");
>
> Context initialContext = new InitialContext(env);
Please suggest.
xg...@yahoo.com
xg...@yahoo.com
I really appreciate your suggetion.
aix...@gmail.com
Does your Connection Factory JNDI correctly match between your admin
console configuration and program? What is it inside admin cosole?
Gareth Matthews
them so that the endpoints are set to
'167.230.98.52:7276:BootstrapBasicMessaging'.
Cheers,
Gareth
<xg...@yahoo.com> wrote in message
news:1580436572.115938185...@ltsgwas010.sby.ibm.com...
xg...@yahoo.com
I am thinking about this configuration. As I found while digging ....
1. How do I make my client to communicate through bootstrap server? because my standalone client is running outside of app server, do i really need
some other configuration on the client side, which is just plain java class and running from the command prompt.
Currently, my client code is like this.
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://localhost:2809");
Context initialContext = new InitialContext(env);
ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("myconnectionfactory");
Queue queue = (Queue)initialContext.lookup("myqueue");
Connection conn = connectionFactory.createConnection();
2. What would be my configuration Scope, Cell, Node or Server?
Please put your thought and let me know if I am missing something.
I am really struggling.
xg...@yahoo.com
I am not sure why it is blowing up with the standalone code ????
Any expert ??
Stephen Cocks
connection factory to allow the standalone client program to find a server
through which it can locate a messaging engine for the requested bus. When
you run the same code within a JSP the provider endpoint setting is ignored
if information about the requested bus is known to that server's
environment. Thus getting the code to work from within a JSP doesn't prove
that all the configuration is correct.
It's quite common for servers created within RAD not to have the default
ports, especially if you have multiple servers or a full runtime
installation on the same machine. How many installations, profiles, and
servers do you have on your machine? Are you sure that the server in the UTE
is using 7276 for its messaging support (SIB_ENDPOINT_ADDRESS) [check the
server details via the admin console to see the port settings]?
--
Stephen Cocks
WESB/WPS System Administration
<xg...@yahoo.com> wrote in message
news:10734640.1159459539...@ltsgwas010.sby.ibm.com...
xg...@yahoo.com
I agree with you about Provider Endpoint which needs to configured correctly if I am running standalone client program.
Now, to configure the Provider Endpoint, I have entered 167.230.98.52:7276:BootstrapBasicMessaging. Below is the port configured for this server, I have listed to make sure I am putting the right port number for Provider Endpoint i.e., 7276. I havenot changed anything, everythihg is default.
BOOTSTRAP_ADDRESS 2809
SOAP_CONNECTOR_ADDRESS 8880
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 9401
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 9403
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 9402
WC_adminhost 9060
WC_defaulthost 9080
DCS_UNICAST_ADDRESS 9353
WC_adminhost_secure 9043
WC_defaulthost_secure 9443
SIB_ENDPOINT_ADDRESS 7276
SIB_ENDPOINT_SECURE_ADDRESS 7286
SIB_MQ_ENDPOINT_ADDRESS 5558
SIB_MQ_ENDPOINT_SECURE_ADDRESS 5578
ORB_LISTENER_ADDRESS 9100
And, I think rest of the configuration will remain the same. Is there something that I am missing ???
....
aix...@gmail.com
admin console?
What is your coding for JMS.
Stephen Cocks
If you want to post more details about your standalone client project setup
(classpath, how invoked, etc), or the full configuration of all the
properties on your Connection Factory then it may reveal something. We could
start talking about enabling trace to see if additional information is
logged. But it may simply be time to raise a PMR through the formal support
channels.
--
Stephen Cocks
WESB/WPS System Administration
<xg...@yahoo.com> wrote in message
news:1720552642.115946867...@ltsgwas010.sby.ibm.com...
xg...@yahoo.com
2. Bus members -> assigned server to bus(Node=GSO0495809DNode01, Server=server1 )
message engine is running.
3. JMS Providers -> Default messaging -> Queue Connection Factory
Name : My Queue Connection Factory
JNDI Name: myQCF
BusName : myBus
Provider endpoints : 167.230.98.52:7276:BootstrapBasicMessaging
I am not putting queue info because my problem is on QCF.createConnection()
Standalone Client Program runing from RAD after adding all jars of websphere in the classpath
----------------------------------------------------------------------------------------------
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://localhost:2809");
Context initialContext = new InitialContext(env);
ConnectionFactory connectionFactory = (ConnectionFactory)initialContext.lookup("myQCF");
log("creating connection ..");
Connection conn = connectionFactory.createConnection();
To verify my JMS Configuration, I tested with JSP and MDB, all working fine except Standalone client.
If you need, any more info please let me know.
Thanks
monster910
Scenario
1. My sample works with launchClient.bat against a RAD Test Server (localhost:2809) and my WAS 6.0.0 solaris server bootstrap port 9811.
2. I installed the JMS client code. I installed the SUN JDK version. I am using JDK 1.4.2.
http://www-1.ibm.com/support/docview.wss?uid=swg24012804
3. I recompiled the PackageReceivedClient from step 1. I changed some naming because it is not running in a J2EE space. (i.e. remove the java:comp/env/ prefix).
4. I run via
"C:\j2sdk1.4.2_12\jre\bin\java" %WAS_TRACE% %WAS_FFDC% -classpath "C:\j2sdk1.4.2_12\jre\lib;c:\ibm\jms\properties;C:\j2sdk1.4.2_12\lib\tools.jar;PackageReceivedClient.jar" -Djavax.net.ssl.keyStore=c:\ibm\jms\etc\DummyClientKeyFile.jks -Djavax.net.ssl.keyStorePassword=WebAS -Djavax.net.ssl.trustStore=c:\ibm\jms\etc\DummyClientTrustFile.jks -Djava.ext.dirs="C:\j2sdk1.4.2_12\jre\lib;C:\j2sdk1.4.2_12\jre\lib\ext;c:\ibm\jms\lib" -Djava.naming.provider.url=iiop://localhost:2809 -Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory sender.Main
localhost=latituded600=127.0.0.1
4. The code fails on something with endpoints. AND YES, I have them configured with the correct ports. On my localhost they are localhost:7276:BootstrapBasicMessaging and on my server devappzone1:7278:BootstrapBasicMessaging. YES, 7278 is correct.
Snip from trace.log
[18/10/2006 13:36:00:211 CDT] 3e97df com.ibm.ejs.util.am.AlarmManagerThread 3 Alarm manager thread waiting 9980
[18/10/2006 13:36:00:211 CDT] 137c60d com.ibm.ws.sib.comms.client.ClientSideConnection 3 [:/90d8ea] Connection dropped: com.ibm.wsspi.sib.core.exception.SIConnectionDroppedException: CWSIJ0047E: An operation was attempted on a connection that is already closed.
[18/10/2006 13:36:00:211 CDT] 137c60d com.ibm.ws.sib.utils.ras.SibMessage Warning: [:] CWSIT0007W: It is not possible to contact the bootstrap server at latituded600:7276:BootstrapBasicMessaging because of exception: com.ibm.websphere.sib.exception.SIResourceException: com.ibm.wsspi.sib.core.exception.SIConnectionDroppedException: CWSIJ0047E: An operation was attempted on a connection that is already closed..
[18/10/2006 13:36:00:211 CDT] 137c60d s.sib.trm.client.TrmSICoreConnectionFactoryImpl2 3 [:] Run through all the available endpoints, goodReply=false
[18/10/2006 13:36:00:211 CDT] 137c60d s.sib.trm.client.TrmSICoreConnectionFactoryImpl2 3 [:] Unable to contact a bootstrap server TheBus[latituded600:7276:BootstrapBasicMessaging][]
[18/10/2006 13:36:00:221 CDT] 137c60d com.ibm.ws.ffdc.FFDCFilter 3 FFDC exception: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to connect to bus TheBus because the following bootstrap servers could not be contacted [latituded600:7276:BootstrapBasicMessaging] and the following bootstrap servers returned an error condition []. See previous messages for the reason for each bootstrap server failure. sourceId=com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.createManagedConnection (Subject, ConnectionRequestInfo) probeId=6 caller=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl@2715510 <managedConnectionFactory=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaManagedConnectionFactoryImpl@20736546 <logWriter=java.io.PrintWriter@54c4ad> <busName=TheBus> <clientID=> <userName=null> <password=null> <xaRecoveryAlias=null> <nonPersistentMapping=ExpressNonPersistent> <persistentMapping=ReliablePersistent> <durableSubscriptionHome=> <readAhead=Default> <temporaryQueueNamePrefix=> <temporaryTopicNamePrefix=> <target=> <targetSignificance=Preferred> <targetTransportChain=> <targetType=BusMember> <providerEndpoints=latituded600:7276:BootstrapBasicMessaging> <connectionProximity=Bus> <shareDataSourceWithCMP=false> <shareDurableSubscriptions=InCluster> <cachedFactory=com.ibm.ws.sib.api.jms.impl.JmsFactoryFactoryImpl@cafb56>]> <connectionManager=null> <managed=false>]
[18/10/2006 13:36:00:221 CDT] 137c60d s.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl Event: [:/296f76] Tracing exception:
com.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to connect to bus TheBus because the following bootstrap servers could not be contacted [latituded600:7276:BootstrapBasicMessaging] and the following bootstrap servers returned an error condition []. See previous messages for the reason for each bootstrap server failure.
at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl2.bootstrapRequest(TrmSICoreConnectionFactoryImpl2.java:607)
at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl2.remoteBootstrap(TrmSICoreConnectionFactoryImpl2.java:404)
at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl2.createConnection(TrmSICoreConnectionFactoryImpl2.java:239)
at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl2.createConnection(TrmSICoreConnectionFactoryImpl2.java:144)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.createCoreConnection(JmsJcaConnectionFactoryImpl.java:545)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.createCoreConnection(JmsJcaConnectionFactoryImpl.java:481)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.createConnection(JmsJcaConnectionFactoryImpl.java:302)
at com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:206)
at com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:159)
at sender.JMSClient.<init>(JMSClient.java:64)
at sender.Main.main(Main.java:32)
Any ideas?
Paul Ilechko
> I have having the exact same issue. I have been working on this 2.5 days. I even had an IBM consultant work on this one. No luck.
>
> Any ideas?
>
>
>
open a PMR
monster910
The JMS client was released in Aug 2006.
Upgrade your WAS to 6.0.2.15
Upgrade your RAD to the latest
abel...@gmail.com
My advice is:
pay atention on the Application Client's and the Application Server's versions. The versions MUST be the same (including all pathes and fixes).
BTW there is a known issue described here http://www-1.ibm.com/support/docview.wss?uid=swg21211800
shereen...@gmail.com
<br />
I realize this is a year later than the topic had originally been discussed but, then maybe it's a good thing since many have experimented. <br />
<br />
I am encountering this exception that is having me go around in circles. I have two servers, Server1 hosts my application and Server2 has myBus and myQueue. I created a queue connection factory on Server1 with provider endpoint: <server2-ip>:7276:BootstrapBasicMessaging. When I try running the application it crashes and gives me the following exception:<br />
<br />
Failed to Send Object Message: CWSIA0062E: Failed to create a MessageProducer for queue://jms/myQueue<br />
<strike>2/3/08 17:38:54:205 GST</strike> 00000048 SystemErr R javax.jms.InvalidDestinationException: CWSIA0062E: Failed to create a MessageProducer for queue://jms/myQueue<br />
..<br />
Caused by: com.ibm.websphere.sib.exception.SINotPossibleInCurrentConfigurationException: CWSIC8007E: An exception was caught from the remote server with Probe Id 3-008-0001. Exception: CWSIK0015E: The destination jms/myQueue was not found on messaging engine Node01.server1-myBus..<br />
<br />
I feel like it is connecting to myBus on Server2 properly it's just having trouble finding myQueue. Is there something in particular that I need to do so that it can see myQueue?<br />
<br />
I would appreciate anyone's help!
Stephen Cocks
? Or did you name it "myQueue"?
It looks like you are using JNDI to find the locally created Queue
Connection Factory which subsequently connects you to the Messaging Engine
Node01.server1-myBus. The ME/bus is then looking for a destination
"jms/myQueue" which it doesn't find. I assume you are creating the JMS
Destination object programmatically from the URI "queue://jms/myQueue" and
not using JNDI to look up an admin object for the destination?
If none of the above helps fix the problem, then please provide full
information on your environment. You've said you have a Node01.server1 on
Server2 (I assume therefore that Server2 is a computer name and not the name
of an application server). What node(s)/server(s) do you have on Server1?
Are your application servers configured in an ND cell, or are they both
standalone (default) application servers?
What versions of WebSphere Application Server are you using?
--
Stephen Cocks
WESB/WPS System Administration
<shereen...@gmail.com> wrote in message
news:1640631546.120205775...@ltsgwas009.sby.ibm.com...
swamy...@yahoo.co.uk
My requirement is is to send a message remote from pc to antother.
I have configured with WS 6.0 on the both pc with different QCF, Queue, Activation specification, Bus Name, Froeign Name, SIB Lins i have created to communicte b/w the pc's. When i give destination queue with SIB links, its giving the following exception, please help on this issue how to resolve.
many thins in advance.
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R javax.jms.InvalidDestinationException: CWSIA0062E: Failed to create a MessageProducer for queue://MDBQueue?busName=MDBBus&readAhead=AlwaysOn
at com.ibm.ws.sib.api.jms.impl.JmsMsgProducerImpl. (JmsMsgProducerImpl.java:380)
at com.ibm.ws.sib.api.jms.impl.JmsQueueSenderImpl. (JmsQueueSenderImpl.java:78)
at com.ibm.ws.sib.api.jms.impl.JmsQueueSessionImpl.instantiateProducer(JmsQueueSessionImpl.java:359)
at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.createProducer(JmsSessionImpl.java:1038)
at com.ibm._jsp._index2._jspService(_index2.java:92)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2837)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:94)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
Caused by: com.ibm.websphere.sib.exception.SINotPossibleInCurrentConfigurationException: CWSIK0015E: The destination MDBQueue was not found on messaging engine dav11877jy72jNode01.server1-MDBBus.
at com.ibm.ws.sib.processor.impl.DestinationManager.checkDestinationHandlerExists(DestinationManager.java:3968)
at com.ibm.ws.sib.processor.impl.DestinationManager.getDestination(DestinationManager.java:1316)
at com.ibm.ws.sib.processor.impl.ConnectionImpl.internalCreateProducerSession(ConnectionImpl.java:1135)
at com.ibm.ws.sib.processor.impl.ConnectionImpl.createProducerSession(ConnectionImpl.java:959)
at com.ibm.ws.sib.api.jms.impl.JmsMsgProducerImpl. (JmsMsgProducerImpl.java:352)
... 23 more
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsMsgProducerImpl. (JmsMsgProducerImpl.java:380)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsQueueSenderImpl. (JmsQueueSenderImpl.java:78)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsQueueSessionImpl.instantiateProducer(JmsQueueSessionImpl.java:359)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.createProducer(JmsSessionImpl.java:1038)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm._jsp._index2._jspService(_index2.java:92)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2837)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:94)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R Caused by: com.ibm.websphere.sib.exception.SINotPossibleInCurrentConfigurationException: CWSIK0015E: The destination MDBQueue was not found on messaging engine dav11877jy72jNode01.server1-MDBBus.
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.processor.impl.DestinationManager.checkDestinationHandlerExists(DestinationManager.java:3968)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.processor.impl.DestinationManager.getDestination(DestinationManager.java:1316)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.processor.impl.ConnectionImpl.internalCreateProducerSession(ConnectionImpl.java:1135)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.processor.impl.ConnectionImpl.createProducerSession(ConnectionImpl.java:959)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsMsgProducerImpl.(JmsMsgProducerImpl.java:352)
[16/09/08 12:47:52:682 BST] 00000049 SystemErr R ... 23 more
Mike Dunk
The server configuration has not changed and the Provider endpoint field has been set on the connection factory to localhost:7279:BootstrapBasicMessaging.)
Went through chapter 2 and chapter 6 of JMS Problem Determination redpaper [http://www.redbooks.ibm.com/redpieces/pdfs/redp4330.pdf)]
Finally solved it by creating a new profile using pmt.bat.
Mike Dunk
Have not tried out this for myself but was told by a co-worker that a better solution is to load the JMS queue with a client program that does not use any IBM classes. So I guess it's down to someone who encounters this again to raise a PMR.