Problems with Xerces2 and xalan
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Anonymous
Posted On:   Monday, November 5, 2001 08:42 AM

Hi, I am calling a finder method from my session bean to filter through all emails in our database. Transaction times out after 299 seconds. I've increased the timeout for transactions but I still get this problem. Here is the stack trace: Exception: java.rmi.RemoteException: EJB Exception:; nested exception is: java.rmi.RemoteException: ConfirmationSenderBean:remind()javax.ejb.FinderException: Exception in 'findByRemindersToBeSent' while using result set: 'weblogic.jdbc.rmi.SerialResultSet@43b641' java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds 41]'. No further JDBC access is allowed within this transaction   More>>

Hi,
I am calling a finder method from my session bean to filter through all emails in our database. Transaction times out after 299 seconds. I've increased the timeout for transactions but I still get this problem. Here is the stack trace:

Exception: java.rmi.RemoteException: EJB Exception:; nested exception is: java.rmi.RemoteException: ConfirmationSenderBean:remind()javax.ejb.FinderException: Exception in 'findByRemindersToBeSent' while using result set: 'weblogic.jdbc.rmi.SerialResultSet@43b641' java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds 41]'. No further JDBC access is allowed within this transaction. java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds 41]'. No further JDBC access is allowed within this transaction. at weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:531) at weblogic.jdbc.jts.ResultSet.next(ResultSet.java:279) at weblogic.jdbc.rmi.internal.ResultSetImpl.next(ResultSetImpl.java:135) at weblogic.jdbc.rmi.internal.ResultSetStraightReader.next(ResultSetStraightReader.java:27) at weblogic.jdbc.rmi.SerialResultSet.next(SerialResultSet.java:73) at com.sopha.contactmanager.AccountEmailBean_kd7pfz__WebLogic_CMP_RDBMS.ejbFindByRemindersToBeSent(AccountEmailBean_kd7pfz__WebLogic_CMP_RDBMS.java:1364) at java.lang.reflect.Method.invoke(Native Method) at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.collectionFinder(RDBMSPersistenceManager.java:314) at weblogic.ejb20.manager.BaseEntityManager.collectionFinder(BaseEntityManager.java:739) at weblogic.ejb20.manager.BaseEntityManager.collectionFinder(BaseEntityManager.java:712) at weblogic.ejb20.internal.EntityEJBLocalHome.finder(EntityEJBLocalHome.java:476) at com.sopha.contactmanager.AccountEmailBean_kd7pfz_LocalHomeImpl.findByRemindersToBeSent(AccountEmailBean_kd7pfz_LocalHomeImpl.java:193) at com.sopha.util.ConfirmationSenderBean.remind(ConfirmationSenderBean.java:76) at com.sopha.util.ConfirmationSenderBean_w88a3a_EOImpl.remind(ConfirmationSenderBean_w88a3a_EOImpl.java:45) at com.sopha.util.ConfirmationSenderBean_w88a3a_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229) at com.sopha.util.ConfirmationSenderBean_w88a3a_EOImpl_WLStub.remind(Unknown Source) at jsp_servlet._rome.__testmail._jspService(__testmail.java:208) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:445) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

I have an encoding problem with xerces2 .


I recently upgraded my xerces jar because because it was required by
xalan . I use xalan to convert one xml-message into another. That part works fine. The conversion routine works fine that's not the problem.


My problem is that when I use the DOM parser of Xerces it ignores the encoding (I use US-ASCII ). No matter what encoding I use, high ascii characters are not read in correctly.


I tried playing with some features but without success.


Any ideas?

   <<Less

Re: Problems with Xerces2 and xalan

Posted By:   Shane_Curcuru  
Posted On:   Friday, November 9, 2001 12:43 PM

Hmmm - I'm a little confused, especially since no publicly shipped builds of Xalan yet require (or until today) even advertised Xerces 2.x support.

I'd suggest double-checking your encoding (i.e. are you positive that the characters you are using are both in that encoding and are legal XML characters?) and investigating more on one of the Xerces support lists.

About | Sitemap | Contact