JMS Channel Error with ActiveMQ

Hi Experts,
currently I am facing an issue thats driving me crazy.
I configured JMS Adapter for activeMQ as per this [guide|http://www.sappi.sapag.co.in/sap-pi-7-1-ehp-1-and-microsoft-net-framework-3-5/activemq-free-but-yet-powerful-jms-provider/]
Deployed the external drivers as per Note 1138877
Now when I check the Communication Channel Monitoring in PI 7.1 I alway get the error messages "Channel has internal error" and "Adapter has not provided any status information about this channel". In the Administrators Information" Tab I can find the exception "channel with status unknown or unregistered".
I already followed note 1660910 but with no success.
Any idea what else I could check?
Thanks and best regards,
Frank

Hello Frank,
I had the same situation with our PI 7.1. Try to re-deploy JMS driver with older driver release which can be found on http://activemq.apache.org/download-archives.html.
For example, one of our PI 7.1 systems works with ActiveMQ 4.1.1 Release and another with ActiveMQ 5.6.0 Release. I would say that it depends about java runtime version and maybe PI patch level.
Kind Regards,
Kristijan

Similar Messages

Sender JMS Channel Error

Hi all,
I have been facing with this problem with sender JMS channel, any pointers as to where can be the solution for it
The error details are as follows
JMS and XI identifiers for the message are ID:414d512056515933444e41575445202048aa8802235bad01 and a2d32e30-7aae-11dd-ae1c-001125cc0c0c respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception
at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:963)
at com.ibm.mq.jms.MQMessageConsumer.receiveAsyncQ(MQMessageConsumer.java:2539)
at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4262)
Messages are not being placed in the Queue. the Queues are newly created is there something which has been missed out during the creation of the Queues
Rgds
Aditya

Hi Aditya
Try this way:
1. uncheck JMS transactional session check box in JMS sender communication channel.
2. Once it is done, insert new message in JMS queue.
Thanks
Sai

JMS Channel error

JMS Channel is thrrowing error with an error code:2007.
Error code description is "CharAttrs is not valid. The parameter pointer is not valid, or points to read-only storage for MQINQ calls or to storage that is not as long as implied by CharAttrLength. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)".
But i didnt understood this jargon.
Could anyone help me what i need to do to fix this .
Thanks in advance.

Hi Pola,
I have never faced this error but as in my helping nature here are some pointers:
CharAttrLength (MQLONG) - input
Length of character attributes buffer.
This is the length in bytes of the CharAttrs parameter, and must be at least the sum of the lengths of the character attributes specified in the Selectors array. Zero is a valid value if there are no MQCA_* selectors in Selectors.
CharAttrs (MQCHAR×CharAttrLength) - input
Character attributes.
This is the buffer containing the character attribute values, concatenated together. The length of the buffer is given by the CharAttrLength parameter.
The characters attributes must be specified in the same order as the MQCA_* selectors in the Selectors array. The length of each character attribute is fixed (see Selectors). If the value to be set for an attribute contains fewer nonblank characters than the defined length of the attribute, the value in CharAttrs must be padded to the right with blanks to make the attribute value match the defined length of the attribute.
If the CharAttrLength or SelectorCount parameter is zero, CharAttrs is not referred to; in this case, the parameter address passed by programs written in C or System/390 assembler may be null.
Regards
joel

JMS Channel error reson code : 2019

JMS Channel is throwing error with an reason code : 2019.
Decription for reason code 2019 is : The object handle Hobj is not valid, for one of the following reasons:
The parameter pointer is not valid, or (for the MQOPEN call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
The value specified was not returned by a preceding MQOPEN call.
The value specified has been made invalid by a preceding MQCLOSE call.
The handle is a shared handle that has been made invalid by another thread issuing the MQCLOSE call.
The handle is a nonshared handle that is being used a thread that did not create the handle.
The call is MQGET or MQPUT , but the object represented by the handle is not a queue.
Can any one tell me what is to be done to fix this error.
Thanks in advance.

Hi
Yes this is an MQ Series "Reason Code", Where each reason code for failing is assigned a number. For this one please refer to the following link:
http://www-01.ibm.com/support/docview.wss?uid=swg21229508
For all reason codes have a look at:
http://middleware.its.state.nc.us/middleware/Documentation/en_US/htm/csqzak06/csqzak065m.htm
Thanks
Damien

JMS Sender Channel Error with MQ Series

Hi,
I am trying to send a message from MQ Series to XI via JMS Adapter. I am getting this error message, and I have searched the forums for this error message with no luck. Can someone please help? I have asked the BASIS team to double check and make sure the JMS drivers have been deployed. I am still waiting for their reply.
Thanks in advance
Zeshan Anjum

Sorry, I forgot to append the error message.
Here it is:
0 XI inbound processing failed for message at 2006-10-19|09:54:30.925-0500. JMS and XI identifiers for the message are ID:414d51205a3153505420202020202020448dda5420003f01 and b9be54c0-5f81-11db-a551-001125a6015a respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Value with name enableDynConfigSender not available
at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java(Compiled Code))
at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java(Compiled Code))
at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java(Compiled Code))

Receiver JMS Channel Error

hi,
I am facing an issue with the JMS Receiver Communication channel.Data is not getting inserted in the JMS Queue.CC Monitoring is showing the below ERROR:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_r_CustomerLedgeron node: 7065651 having object id: 340fa47e4dc33a04a4f8a5a108708f07 encountered error: Error sending message in sending to destination custLedgerReplication, the message message: TextMessage[null, <?xml version="1.0" encoding="...]: weblogic.jms.common.JMSException: Error sending message.
can someone helpme out.
thanks,
robin

Hello Robin,
did you resolve this issue? I have now the same problem.
Do you have connections with two (or more) BEA servers using the same Adapter Framework?
Note 1090516 describes a problem with credentials confusion when connecting to more servers.
It could be the cause.
With regards
Tomas

Communication Channel Error with MDM PI Adapter

Dear Experts,
We had new sever for PI(image copy). In new PI server we are facing problem only with MDM adapterin communication channel monitoring and below error occuring.
*" MDM Adapter listener could not start due to: Can not create repository session '<server=SAPMDMD serverUser=Admin repository=TTSL_Vendor_Dev user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'SAPMDMD' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer "
Any expert please help us to resolve this.
Thanks in advance.
Regards,
Hemu.

Hello Heymanth,
Make sure that connection is fine between systems. Test the RFC's in both systems. Also check the services too.
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario
/people/ramesh.gulipalli2/blog/2009/11/16/sap-47-to-mdm-integration-using-pi71-part1
Regards
Pothana

" Could not create SSL/TLS secure channel " error with Webtest of VS 2013

hello !
I want to test my mvc web project with webtest tools of VS 2013 and I Record a test with Internet Explorer
but when I run test appear this error for me at result of test run : Could not create SSL/TLS secure channel
for some requested url , but i watch requests in developer tools of chrome browser and I don't see this error.
i have ssl certificate on the server.
thanks

Hi ArashGhf,
>>but when I run test appear this error for me at result of test run : Could not create SSL/TLS secure channel
Based on the error message, it looks like it might be a problem with your certificate not being set up correctly for web performance test.
Therefore, I suggest you could refer the autom8dTest's suggestion to convert the Web performance test to coded web performance test and then add the WebTestRequest ClientCertificates property to the ClientCertificates collection after the request
is set up.
For more information, please refer to it.
https://social.msdn.microsoft.com/Forums/en-US/49e8d188-90c3-4d72-b387-10b1d1adc4a0/ssl-in-webtests-request-failed?forum=vstswebtest
Hope it help you!
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error with JMS receiver channel

Hi,
We have a scenario in which Order response will be sent from ECC to WebLogic (JMS system) through PI.
After the restart of JMS, we are facing issues with JMS receiver channel.
Some of the responses are delivered, and for few we have the error as described below.
Also, one of the cluster node of the JMS receiver channel has the below error.
Please anybody throw some light on this.
Error description:
" Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Pending message discovered: dfff2e2b-80f5-94f1-a068-001cc4d99b3e.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards.. "
Thanks in advance.
Regards
Bhanu Tiruveedula.

Hello Bhanu,
we have been getting this error from long time with JMS channel but no solution except changing the configuration so that it can throw exception and move on.
we have also noticed that this happens for some time and then gets resolved automatically. so it seems to be some data which is not expectable by jms channel.
regards,
Ratna

Error in JMS channel

Hi ALL,
I am getting the below error in Communication channel monitoring short log of JMS channel.
"Cannot connect because class 'com.ibm.mq.jms.MQQueueConnectionFactory' is missing; ensure that JMS provider library 'aii_af_jmsproviderlib.sda' contains all required resources"
This error looks like the deployed .sda file dint contain the class specified.Can u let me know where i can find the aii_af_jmsproviderlib.sda file with all required classes in it .
We are on SAP XI 7.0 SP 14 and the MQ version is 7.0.
Kindly let me know if any one had faced the same error.
Regards,
Rajesh

Hi, check this links.
XI to IBM Websphere Default JMS Provider with JNDI
JMS receiver adapter configuration error
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Edited by: Marco Salazar on Dec 9, 2009 5:24 PM

Error with the Receiver JMS Adapter (Connection On-Demand feature)

Hi,
In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
The message status was set to WAIT.
Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
Any idea?
PI 7.1 EHP1
Thanks,
Martin
/people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PM

Please ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).

Server Error with JMS

I have installed..WSAD5.1.2 with 5.0 Test Environment and IBM WebSphere MQ 5.3.
I have created a PointToPoint Messaging Client. with a QueueConnectionFactory n Queue JNDI name.
I am getting following problems during the server startup...
*** Starting the server ***
************ Start Display Current Environment ************
WebSphere Platform 5.0 [BASE 5.0.2 ptf2M0325.01] running with process name localhost\localhost\server1 and process id 2088
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.3.1 IBM Windows 32 build cn131-20030711a (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5
user.install.root = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5
Java Home = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\java\jre
ws.ext.dirs = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/lib;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/classes;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/classes;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/ext;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/web/help;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.webservice_5.1.2/runtime/worf.jar
Classpath = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/properties;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/properties;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/bootstrap.jar;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/j2ee.jar;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/lmproxy.jar;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wteServers.jar;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wasToolsCommon.jar
Java Library path = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/jre/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;.;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;C:\IBM\WebSphere MQ\Java\lib;C:\dev\MKS\IntegrityClient\bin;c:\dev\Perl\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\dev\cygwin\bin;C:\dev\4NT302;C:\dev\apache-ant-1.5.4\bin;C:\dev\jdk1.3.1_08\bin;C:\dev\jakarta-tomcat-4.1.30\bin;C:\dev\mksscripts\src;C:\tbs\bin;C:\Program Files\IBM\WebSphere MQ\WEMPS\bin;c:\dev\MQ\bin;C:\IBM\WebSphere MQ\Java\bin;C:\IBM\WebSphere MQ\WEMPS\bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\bin;C:\IBM\WebSphere MQ\bin;;C:\IBM\WebSphere MQ\bin;C:\IBM\WebSphere MQ\Java\bin;C:\IBM\WebSphere MQ\WEMPS\bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\bin;.;C:\dev\NMake;C:\dev\ZipUnzip;
************* End Display Current Environment *************
[6/7/04 11:59:06:000 IST] 4eee356d ManagerAdmin I TRAS0017I: The startup trace state is *=all=disabled.
[6/7/04 11:59:06:516 IST] 4eee356d AdminInitiali A ADMN0015I: AdminService initialized
[6/7/04 11:59:07:500 IST] 4eee356d Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
[6/7/04 11:59:07:547 IST] 4eee356d SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
[6/7/04 11:59:07:641 IST] 4eee356d SecurityCompo I SECJ0309I: Java 2 Security is disabled.
[6/7/04 11:59:07:656 IST] 4eee356d SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[6/7/04 11:59:07:656 IST] 4eee356d SecurityCompo I SECJ0240I: Security service initialization completed successfully
[6/7/04 11:59:09:797 IST] 4eee356d JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager
[6/7/04 11:59:11:125 IST] 4eee356d JMSEmbeddedPr A MSGS0051I: Queue Manager open for business
[6/7/04 11:59:11:125 IST] 4eee356d JMSEmbeddedPr A MSGS0052I: Starting the Broker
[6/7/04 11:59:11:297 IST] 4eee356d SystemErr R MQJE001: Completion Code 2, Reason 2085
[6/7/04 11:59:11:297 IST] 4eee356d BrokerManager E MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
[6/7/04 11:59:11:328 IST] 4eee356d JMSService E MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1527)
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1579)
at com.ibm.ws.messaging.BrokerManager.attachToMQ(BrokerManager.java:439)
at com.ibm.ws.messaging.BrokerManager.startBroker(BrokerManager.java:234)
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:194)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Please let me know what is the problem and how to solve it. This is urgent. Tnx

Did you go into Websphere MQ and set up the queue you are using? Defining the queue in JNDI is not enough.
Broker Manager unable to attach to Queue Manager - unknown Queue

JMS Adapter Error

Hi Experts,
               We are havingone problem in Sender JMS Adapter. From Sender (SeeBeyond) xml files are getting posted into Remote Queue in MQ, then it has been sent to Local Queue of MQ, and then finally from Local MQ Queue PI is picking up the data and sending it to SNC system.
               The problem lies in PI itself. While coming into PI, the value in the incoming payload where special characters(say, swedish character) are coming, are coming into PI as a garbage value. Whereas, in Sender (SeeBeyond), MQ and in PI Character set is ISO 8859_1. We have stopped the Sender JMS channel in PI, and checked the payload in MQ and in SeeBeyond, in both of the cases it's fine, only when coming into PI, data are getting corrupted.
                For this we have done some investigation like below,
1) We had changed the CCSID from 00819 (ISO 8859_1) to 1208 (UTF-8), 1200 (UTF 16), but no luck.
2) We had added th below mentioned modules into Sender JMS in Processing Sequence with the existing modules,
AF_Modules/MessageTransformBean                                              Local Enterprise Bean               ContentType
(ii) AF_Modules/TextCodepageConversionBean                                   Local Enterprise Bean               codepageConversion
But yet we are getting the same error in encoding in the payload while coming into PI.
Can anybody help me out with it, or probably let me know if I am missing something in my investigation.
//BR
Soumya

Hi Stefan,
             Sorry for the late reply. We were testing in different cases in PI, and here what I have found. In Sender JMS adapter we had put the module "AF_Modules/MessageTransformBean" with Module Key "Transform". And the configuration of this Module Key is as follows:-
Transform     Transform.ContentType      text/plain;charset="UTF-8"
And we changed the CCSID to 1208 (UTF-8). Now when we saw the payload in SXI_MONITOR in PI, we have found that the special character is being distorted whereas in View Sourse the payload is fine including special character also. That means there might be some display problem in SXI_MONITOR.
             Now, the Sender sends the data in XML iin ISO 8859-1nto MQ, MQ send the same as a string in PI, from PI it's going to SCM system (R/3, Supply Chain Management), where we could see ABAP.APPLICATION Error. We tested the interface in SCM system by running SPROXY and found that it's not able to recognise ISO 8859-1, since it's a Non-Unicode System, it will only understan UTF-8 and hence the error. Now manually we have changed the XML Header into UTF-8 and tested at SCM side, and this goes fine.
           So, we could see the changing of XML Header from ISO 8859-1 to UTF-8 would be running fine at receiver end (SCM). Since SCM is a Non-Unicode System, the XML header cannot be changed to UTF-8, is there any possibility in PI that we can change the XML Header from ISO 8859-1 to UTF-8.
           For your information, we are using Sender JMS adapter to receive the File from Sender and we are using Receiver XI adapter to post the file into SCM system.
What's your suggestion Stefan, how can we change the XML Header from ISO 8859-1 to UTF-8 in PI?
Many Thanks
Soumya

JMS Adapter Error after installing Websphere MQ 7.1 Drivers ?

Hi,
I have installed 2 ibm websphere mq 7.1 drivers into "com.sap.aii.adapter.lib.sda" and deployed using JSPM.
but then after that all my others jms (using JNDI) that previously working fine become error (in red colour).
The error message is :
Channel has internal error, Adapter has not provided any status information about this channel
The jar file are :
com.ibm.mq.jar
com.ibm.mqjms.jar
After i remove back those 2 files the other jms channel back to green colour except those using websphere mq with error missing class file because no driver installed.
please advise.
Thank you and Best Regards
FYI : I am using PI 7.1 EHP1 SP03

Hello,
I'm facing the same error. I searched jar files of MQSeries 7.0 where WS Application Server is installed but I couldn't find those:
CL3Export.jar
CL3Nonexport.jar
connector.jar
fscontext.jar
providerutil.jar
rmm.jar
when required files are:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.headers.jar
com.ibm.mq.jar
com.ibm.mq.jmqi.jar
com.ibm.mq.pcf.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
fscontext.jar
providerutil.jar
rmm.jar
Does any body can tell me where to find or download the files I'm missing?
Thanks a lot!

ORA-03113: end-of-file on communication channel ERROR

After applying Database patch 3095277 to my 9.2.0.1.0 installation
in order to update it to 9.2.0.4.0,I'm getting ORA-03113: end-of-file on communication channel
ERRORS when attempting various tasks. This is a local installation running on a Windows XP Workstation.
I've even tried creating a new test database but the result is the same.
The reason for moving up to 9.2.0.4.0 is so I can start using Advanced Queuing, which I understand had problems in earlier releases.
However before the update I could at least create the JMS queue tables without ERROR whereas now I get the following errors when attempting to create a queue table in SQL Plus from within Enterprise Manager Console.
SQL*Plus: Release 9.2.0.4.0 - Production on Thu Sep 18 08:20:08 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
BEGIN SYS.DBMS_AQADM.CREATE_QUEUE_TABLE(Queue_table=> 'JMSQTBL',Queue_payload_type=>'SYS.AQ$_JMS_STREAM_MESSAGE',multiple_consumers=> false); END;
ERROR at line 1:
ORA-03113: end-of-file on communication channel
BEGIN SYS.DBMS_AQADM.CREATE_QUEUE(Queue_name=> 'JMSQUE',queue_table=> 'JMSQTBL'); END;
ERROR at line 1:
ORA-03114: not connected to ORACLE
I would be grateful of any pointers as to how to resolve this problem.
Regards
Gary.

Chris, Thanks for the suggestion,
I took a look in the trace log and found the following entries that point to a ORA-00600 as you mentioned earlier.
This is only a test database so there's no great loss if
I have to re create it, but in saying that I did create a new test02 from scratch and had the same problem.
Is it posible something went wrong when applying the 9.2.0.4.0 patch ?.
Regards
Gary.
Dump file c:\oracle\admin\test01\udump\test01_ora_2556.trc
Wed Sep 17 16:25:14 2003
ORACLE V9.2.0.4.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.1 Service Pack 1, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
Windows 2000 Version 5.1 Service Pack 1, CPU type 586
Instance name: test01
Redo thread mounted by this instance: 1
Oracle process number: 10
Windows thread id: 2556, image: ORACLE.EXE
*** 2003-09-17 16:25:14.046
*** SESSION ID:(7.17) 2003-09-17 16:25:14.031
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** Object defn.s out of sync w/ data
*** 2003-09-17 16:25:14.281
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [qmxiUnpPacked2], [121], [], [], [], [], [], []
Current SQL statement for this session:
select 1
from resource_view
where any_path = '/xdbconfig.xml'
----- PL/SQL Call Stack -----
object line object
handle number name
6A4FA348 6 package body XDB.DBMS_REGXDB
6A504D88 1 anonymous block
6A576AB8 639 package body SYS.DBMS_REGISTRY
6A1DBB6C 1 anonymous block

JMS Channel Error with ActiveMQ

Similar Messages

Maybe you are looking for