Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Stack Overflow by dundro
, 1 year ago
This exception has no message.
via Google Groups by anthony, 1 year ago
via Coderanch by Raef Kandil, 1 year ago
via Stack Overflow by Jonas Byström
, 2 years ago
java.lang.Exception at com.ibm.msg.client.commonservices.trace.Trace.getCurrentPosition(Trace.java:1959) at com.ibm.msg.client.commonservices.trace.Trace.createFFSTString(Trace.java:1898) at com.ibm.msg.client.commonservices.trace.Trace.ffstInternal(Trace.java:1787) at com.ibm.msg.client.commonservices.trace.Trace.ffst(Trace.java:1660) at com.ibm.msg.client.jms.JmsFactoryFactory.getInstance(JmsFactoryFactory.java:214) at com.ibm.mq.jms.MQConnectionFactory.initialiseMQConnectionFactory(MQConnectionFactory.java:3314) at com.ibm.mq.jms.MQConnectionFactory.<init>(MQConnectionFactory.java:283) at com.ibm.mq.jms.MQQueueConnectionFactory.<init>(MQQueueConnectionFactory.java:81) at com.ibm.mq.jms.MQQueueConnectionFactoryFactory.getObjectInstance(MQQueueConnectionFactoryFactory.java:77) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321) at com.sun.jndi.fscontext.RefFSContext.lookup(RefFSContext.java:146) at com.sun.jndi.fscontext.FSContext.lookup(FSContext.java:127) at javax.naming.InitialContext.lookup(InitialContext.java:417) at com.company.Main.main(Main.java:31) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)