Win a copy of Murach's MySQL this week in the JDBC and Relational Databases forum!

V Singh

Greenhorn
+ Follow
since Sep 03, 2007
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by V Singh

Hi,

I have deplyed an application WAS6 server.I get the java.lang.IllegalStateException in the logs when I launch the installed application.

I searched a little on it and learnt that this is a known problem with WAS.
And that the possible solution of the problem is using xerces.jar to parse the xml instead of the default crimson.jar used by WAS.
So I added xerces.jar in the WEB-INF/lib folder of the application, rebuilt the EAR and deployed the resulting EAR in WAS.

But I still get the same error in logs.

Please let me know if I have misunderstood something or doing something incorrect.

Thanks in advance,
Himadri

PS: the error stack in logs is follows-


code:
--------------------------------------------------------------------------------

[8/2/07 12:53:17:562 IST] 000000d5 SystemOut O WSWS3185I: Info: Parsing XML file: C:\Program Files\IBM\WebSphere\AppServer\profiles\default\installedApps\itl-hw-44857aNode01Cell\CTMTFmsEAR.ear\CTMTFMSEngine.war\WEB-INF\wsdl\CTMTFormsEngineService.wsdl[8/2/07 12:53:17:594 IST] 0000003f WSDDPort W WSWS3114E: Error: Internal error.[8/2/07 12:53:17:594 IST] 0000003f WSDDPort W TRAS0014I: The following exception was logged java.lang.IllegalStateException: can't declare any more prefixes in this contextat org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:524)at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)at com.ibm.ws.webservices.engine.utils.XMLUtils.newDocument(XMLUtils.java:487)at com.ibm.ws.webservices.engine.utils.XMLUtils.newDocument(XMLUtils.java:532)at com.ibm.ws.webservices.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:636)at com.ibm.ws.webservices.wsdl.Parser$WSDLRunnable.run(Parser.java:337)at java.lang.Thread.run(Thread.java:568)---- Begin backtrace for Nested Throwablesjava.lang.IllegalStateException: can't declare any more prefixes in this contextat org.xml.sax.helpers.NamespaceSupport$Context.declarePrefix(Unknown Source)at org.xml.sax.helpers.NamespaceSupport.declarePrefix(Unknown Source)at org.apache.crimson.parser.Parser2.processAttributeNS(Parser2.java:1587)at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1436)at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)at com.ibm.ws.webservices.engine.utils.XMLUtils.newDocument(XMLUtils.java:487)at com.ibm.ws.webservices.engine.utils.XMLUtils.newDocument(XMLUtils.java:532)at com.ibm.ws.webservices.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:636)at com.ibm.ws.webservices.wsdl.Parser$WSDLRunnable.run(Parser.java:337)at java.lang.Thread.run(Thread.java:568). java.lang.IllegalStateException: can't declare any more prefixes in this contextat org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:524)at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)at com.ibm.ws.webservices.engine.utils.XMLUtils.newDocument(XMLUtils.java:487)at com.ibm.ws.webservices.engine.utils.XMLUtils.newDocument(XMLUtils.java:532)at com.ibm.ws.webservices.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:636)at com.ibm.ws.webservices.wsdl.Parser$WSDLRunnable.run(Parser.java:337)at java.lang.Thread.run(Thread.java:568)
16 years ago
Hi Guys,

I am able to figure out the error.I hadn't entered the queue name correctly.

Regards,
Vandana
Hi,

I am getting the following exception when I am trying to invoke a MDB through servlet.:-

The Connection Manager received a fatal connection error from the Resource Adaptor for resource JMS$MyMdbConnectionFactory. The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue

[9/11/07 11:44:16:588 IST] 4dfb49e7 MDBListenerIm W WMSG0019E: Unable to start MDB Listener Hello, JMSDestination jms/MyMdbQueue : javax.jms.JMSException: MQJMS2008: failed to open MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:540)
at com.ibm.mq.jms.MQQueueAgent.resolveQueue(MQQueueAgent.java:460)
at com.ibm.mq.jms.MQQueueAgent.getQueueAgent(MQQueueAgent.java:271)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:277)
at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:112)
at com.ibm.mq.jms.MQQueueConnection.createConnectionBrowser(MQQueueConnection.java:775)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:444)

*************************************************************************
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.mq.jms.MQQueueAgent.resolveQueue(MQQueueAgent.java:451)
at com.ibm.mq.jms.MQQueueAgent.getQueueAgent(MQQueueAgent.java:271)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:277)
at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:112)
at com.ibm.mq.jms.MQQueueConnection.createConnectionBrowser(MQQueueConnection.java:775)


I am trying to invoke an MDB thru servlet.I hve checked the QueueConnectionFactory Name,Queue Name,ListenerPort name

Following is the servlet code that invokes MDB


I am getting error on qSession.createSender(queue);
Can anyone please help me with this?


I have made an entry for Connection Factory,Queue name and also have enabled the MQ Simulator for Java Developers in JMS Provider section in the JMS tab in the server.I have also configured the listener port with the queue name and the connection factory on the server setting.
I also checked the queuename and connectionfactory that I use in the lookup but somehow still getting this error


Regards,
Vandana
Hi,

Is there any documentation available which says that default trans-attribute for a method in EJB on WSAD is "required" ?

In case if the trans-attribute for a method is "NotSupported" that means that there is no transaction associated with the method and the transaction timeout value set on the server is of no use to that method? i.e the method would not time as per the transaction timeoput value given on the server.

I am really sorry if I am sounding stupid,but I am new to EJBs and wanted to have this funda of trans-attribute cleared.

Thanks,
Vandana
Thanks for the quick response.Since the trans-attribute in case of 2nd batch job is Notsupported and so it runs in an unspecified transaction context so does that mean that transaction timeout doesn't impact in this while in the case of 1st job,since no trans-attribute is mentioned in deployment descriptor so as you mentioned that default is required so it begins the new transaction and transaction timout comes into picture.

Does this sound correct?
Hi,

We are facing timeout issue in one of the method when running EJB on WAS5.1

The issue is that there are two batch jobs which get executed through this bean.1st batch job method has trans attribute of "<trans-attribute>NotSupported</trans-attribute>" in ejb-jar.xml while the 2nd batch job is not mentioned in the ejb-jar.xml with any trans-attribute.

Both these batch jobs are executed through Servlet/

The transaction timeout value set on the server is 30 minutes.The 1st batch job which has a trans-attribute of "NotSupported".It runs for more than 2 hours with out any issue.But the 2nd batch job when it runs beyond 30 mins,we see the following exception:-

aused by
{
Exception Message : javax.transaction.TransactionRolledbackException:
}
Stack Trace :
{
org.omg.CORBA.TRANSACTION_ROLLEDBACK: javax.transaction.TransactionRolledbackException: vmcid: 0x0 minor code: 0 completed: No
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java(Compiled Code))
at java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled Code))
at com.ibm.rmi.util.ProxyUtil.copyObject(ProxyUtil.java:341)
at com.ibm.CORBA.iiop.UtilDelegateImpl.copyObject(UtilDelegateImpl.java:805)
at javax.rmi.CORBA.Util.copyObject(Util.java:333)
at com.user.lan.wordengine.inf.service._InternalDocumentChart_Stub.performSuccess(_InternalDocumentChart_Stub.java:413)

I am absolutely clueless why 1st batch job is able to run successfully while the 2nd batch job is throwing exception after 30 minutes.

Why does the timeout affect only 2nd batch job and not 1st.

regards,
Vandana