[QA of JBoss Portal] - Re: automating jboss portal admin ui testing usign selenium
by vrockai
what about jboss portal log? shouldn't it be published, too? during the testing i ussually have some errors in the main log output... something like
| 12:08:10,706 INFO [DefaultLoadEventListener] Error performing load command
| org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [org.jboss.portal.identity.db.HibernateRoleImpl#5]
| at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:377)
| at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:145)
| at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195)
| at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103)
| at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878)
|
errors like this are fired quite often
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173904#4173904
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173904
15 years, 8 months
[Design of JBoss Transaction Services] - Re: Error or RuntimeException in Synchronization.afterComple
by wolfc
"adrian(a)jboss.org" wrote : Why?
Because I want to be notified that one of my buggily afterCompletions went wrong. ;-)
"adrian(a)jboss.org" wrote : It's valid for the JTA implementation to do:
|
| Psuedo code:
|
| | commit()
| | {
| | resources.end();
| | synchronizations.beforeCompletion();
| | resources.prepare();
| | log.writeResult(); // HERE we know/record the result of the commit (modulo heuristics)
| | threadPool.submit(commitPhase);
| | removeThreadAssociation();
| | return;
| | }
| |
|
| so the rollback()/commit()/afterCompletion()s could be executed
| after the call to tm/tx.commit() has returned to you.
Shoot, the JTA spec is missing the Corba OTS 2.14.1.2:
"Corba OTS" wrote : Before doing so, however, it first issues after_completion to any registered
| synchronizations and, after all responses are received, replies to the client.
"adrian(a)jboss.org" wrote : it would also be wrong to signal a transaction failure, if it actually committed
| but one of the afterCompletions buggily threw an exception.
Yes, I agree. It would be nice if it had some facility to report warnings of such in a different manner.
Ah well, such is life.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173890#4173890
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173890
15 years, 8 months
[Design of EJB 3.0] - Re: Remoting issue
by HamdurRahman
I am still getting the exception even after adding invokerDestructionDelay.
The log has changed and we can see the IP as well as port number(This is changing) and also the WorkerThread#_ is changing
11:14:41,353 ERROR [ServerThread] WorkerThread#3[150.158.75.156:1406] exception occurred during first invocation
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1784)
at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:691)
at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObjectVersion2_2(JavaSerializationManager.java:121)
at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:95)
at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:120)
at org.jboss.remoting.transport.socket.ServerThread.versionedWrite(ServerThread.java:998)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:781)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:522)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173857#4173857
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173857
15 years, 8 months