We are currently using web-sphere MQ 8.0..4,On linux machine.
Siel application connect to our queue manager with jndi. property and .binding files,earlier application working fine.but application upgraded from version 18 to 19 version also they have upgraded the java version from 1.7 to 1.8,post up gradation, application team facing below error. but we dont see any error in Queue manager logs. error written in application logs.
Application using below upgraded jdk version
D:\>java -version,java version "1.8.0_172",Java(TM) SE Run-time Environment (build 1.8.0_172-b11),Java HotSpot(TM) 64-Bit Server VM (build 25.172-b11, mixed mode)
Application uses MQ to communicate with the external systems. application jndi.property and .binding files
below jar files are related to websphere MQ version 8.0.0.7.
File based (current in config) application team needed the below JAR files, we have given below jar to application team which is related to MQ version 8.0.0.7 to.
a) jms.jar
b) fscontext.jar
c) connector.jar
d) providerutil.jar
e) jta.jar - optional
f) ldap.jar - optional
g) com.ibm.mq.jar (IBM)
h) com.ibm.mqjms.jar (IBM)
i) dhbcore.jar (IBM)- for MQ 7.5
j) com.ibm.mq.commonservices.jar
k) com.ibm.mq.jmqi.jar
l) com.ibm.mq.jms.Nojndi.jar
we have tried to placed the latest MQ client version( MQ client 9.0.0.7) jar files and tried it,but no luck we are facing same issue.
Application team tried placing one JAR at a time.which is available in my queue manager, While they have placed the all the JAR except JMS.Jar application team faced the below error:
ErrorCode = JMS_EXCEPTION
ErrorMessage = Exception: com.ibm.msg.client.jms.DetailedJMSException: JMSFMQ6312: An exception occurred in the Java(tm) MQI.
The Java(tm) MQI has thrown an exception describing the problem.
See the linked exception for further information.; Message: JMSFMQ6312: An exception occurred in the Java(tm) MQI.
StackTrace = com.ibm.msg.client.jms.DetailedJMSException: JMSFMQ6312: An exception occurred in the Java(tm) MQI.
The Java(tm) MQI has thrown an exception describing the problem.
While placed all the Jar files including Jms.jar we get this error:
[SIEL ERROR] Thread[http-nio-8080-exec-13,5,main] [2:36:01.393 PM Tue Jul 23: ] Error:JNdi File
[SIEL ERROR] Thread[http-nio-8080-exec-13,5,main] [2:36:01.393 PM Tue Jul 23: ] Errorjava.lang.NullPointerException
#Josh: We have placed the 4 com.ibm.mq.allclient.jar, jms.jar (most be v2.0), fscontext.jar, and providerutil.jar, jar files post changes we are not getting earlier error( JMSFMQ6312),but now facing different exception in logs,please check below error.
Thread[http-nio-8080-exec-43,5,main] [12:09:06.850 PM Mon Jul 29: ] Receive failed.
[SIEL ERROR] Thread[http-nio-8080-exec-43,5,main] [12:09:06.850 PM Mon Jul 29: ] Exception during Receive:
javax.naming.NameNotFoundException: crmCF
[SIEL ERROR] Thread[http-nio-8080-exec-39,5,main] [12:33:24.911 PM Mon Jul 29: ] Threw SielBusinessServiceException with
ErrorCode = JMS_EXCEPTION
ErrorMessage = Exception: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2002: Failed to get a message from destination 'CRM.CUSTOMER.OUT'.
IBM MQ classes for JMS attempted to perform an MQGET; however IBM MQ reported an error.
Use the linked exception to determine the cause of this error.; Message: JMSWMQ2002: Failed to get a message from destination 'CRM.CUSTOMER.OUT'.
StackTrace = com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ2002: Failed to get a message from destination 'CRM.CUSTOMER.OUT'.
IBM MQ classes for JMS attempted to perform an MQGET; however IBM MQ reported an error.
but we can see channel is running fine,no impact on messages transfer, application team wants to know why they are getting this exception.
AMQ8417: Display Channel Status details.
CHANNEL(SIEL.CLIENT) CHLTYPE(SVRCONN)
CONNAME(xxx.xx.xx.xx) CURRENT
STATUS(RUNNING) SUBSTATE(RECEIVE)
Related
When using Oracle Instant Client 21.7 and using the below json being sent to the Debezium connector, the follow error is generated.
Error message:
Caused by: java.sql.SQLException: No suitable driver found for jdbc:oracle:oci:#//<database-host>:<port>/DB
at java.sql.DriverManager.getConnection(DriverManager.java:689)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at io.debezium.jdbc.JdbcConnection.lambda$patternBasedFactory$0(JdbcConnection.java:191)
at io.debezium.jdbc.JdbcConnection$ConnectionFactoryDecorator.connect(JdbcConnection.java:128)
at io.debezium.jdbc.JdbcConnection.connection(JdbcConnection.java:882)
at io.debezium.jdbc.JdbcConnection.connection(JdbcConnection.java:877)
at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:630)
at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:504)
at io.debezium.connector.oracle.OracleConnection.resolveOracleDatabaseVersion(OracleConnection.java:141)
... 71 more
openjdk version "1.8.0_332"
OpenJDK Runtime Environment (build 1.8.0_332-b09)
OpenJDK 64-Bit Server VM (build 25.332-b09, mixed mode)
Running a later version of Java, the driver worked, but the connector still throws that error.
I've moved the drivers into the correct location, as mentioned here but still no dice.
I am trying to execute a war created in Genexus 15, in a CentOs 7 server with an Apache tomcat 9, the version of jdk is 1.8, I am having an error when I call to an external authentication service of certificates for server and trustore keystore client.
The error is the folowing:
java.lang.IllegalArgumentException: object is not an instance of declaring class
Fin de Ejecucion servicio sin errores
MsgRetornoSOAP: NRO: ERROR -10001error decoding server
certificate: java.lang.ClassCastException:
org.bouncycastle.asn1.DERUnknownTag cannot be cast to
org.bouncycastle.asn1.DERString
Cod retorno
Mensaje Retorno
Error GXSOAP
java.lang.IllegalArgumentException: object is not an
instance of declaring class
gmid: 271431
It seems that is a problem with decodification.
Error detail as following: (stacktrace)
Caused by: com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2009'.
at com.ibm.mq.MQDestination.open(MQDestination.java:310)
at com.ibm.mq.MQQueue.<init>(MQQueue.java:261)
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:2751)
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:2779)
at com.citi.sh.h2h.service.adapter.H2hMqSendReceiveAdapter.connect(H2hMqSendReceiveAdapter.java:79)
... 17 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009
at com.ibm.mq.jmqi.remote.internal.RemoteHconn.getConnection(RemoteHconn.java:884)
at com.ibm.mq.jmqi.remote.internal.RemoteHconn.getCmdLevel(RemoteHconn.java:2698)
at com.ibm.mq.MQDestination.open(MQDestination.java:302)
... 21 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009;AMQ9213: A communications error for 'TCP' occurred. [1=java.net.SocketException[Unrecognized Windows Sockets error: 0: recv failed],4=TCP,5=sockInStream.read]
at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.receive(RemoteTCPConnection.java:1515)
at com.ibm.mq.jmqi.remote.internal.RemoteRcvThread.receiveBuffer(RemoteRcvThread.java:804)
at com.ibm.mq.jmqi.remote.internal.RemoteRcvThread.receiveOneTSH(RemoteRcvThread.java:768)
at com.ibm.mq.jmqi.remote.internal.RemoteRcvThread.run(RemoteRcvThread.java:158)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketException: Unrecognized Windows Sockets error: 0: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.receive(RemoteTCPConnection.java:1505)
... 4 more
In windows 2003 server, my application running as a service to connect MQ to execute message. Some process executed successfully, but some are failed. The above error occurred.
My Java application use JDK1.7 and MQ version is 7.0.1.11
Could you give me some solution to fix this issue? Thank your very much for your help!
IBM MQ v7.0 went out of support on September 30th 2015.
I would suggest that you move to a supported version of IBM MQ. I'm leaving 7.1 out of the list below since it will go out of support on April 30 2017. Note that 7.5 will go out of support on April 30 2018.
MQ 7.5 client
MQ 8.0 client
MQ 9.0 client
If you must continue to use a out of support version I did find some references to the cause of your problem being that the Windows server supports both a IPv4 and IPv6 stacks. The solution was to force the JRE to use IPv4 only by adding the following setting to your Java startup.
-Djava.net.preferIPv4Stack=true
There was no project deployed to the Websphere server, and I have yet to enable security feature on the WebSphere Server 7.0.
Could it be from previous attempts to create a server? I've not been successful. The directory C:\myworkspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\ does not exist because I deleted tmp1 folder in an attempt to clean my server environment. Repeat deleted and reinstalling the server does not help.
Here's the stacktrace:
[11/24/14 11:57:00:930 EST] 0000000e ApplicationMg E WSVR0100W: An error occurred initializing, MyApplication
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.NestedJarException: IWAE0008E An error occurred reading MyApplication.war from C:\myWorkspace
Stack trace of nested exception:
java.io.FileNotFoundException: C:\myworkspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\MyApplication (The system cannot find the path specified.)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:112)
at java.io.FileInputStream.<init>(FileInputStream.java:72)
at
When I start to deploy my application, the build is successful but I get the following error while installing:
[exec] JVMDUMP039I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" at 2013/07/09 13:55:51 - please wait.
[exec] JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError".
[exec] WASX7017E: Exception received while running file "deployStartApp_DEV1.py"; exception information: com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is java.lang.OutOfMemoryError: Java heap space]
[exec] java.lang.OutOfMemoryError: java.lang.OutOfMemoryError: Java heap space
I tried increasing the heap size, but it didn't help. Can anybody help me out? I could not find a solution for deploying on WebSphere 8.0
Since I understand you are using wsadmin to do your deployment you might want to use something like:
wsadmin.bat -javaoption –Xms256m -javaoption –Xmx768m
when calling the wsadmin command.
More on this here and here.