[JBoss JIRA] Created: (JBSEAM-344) Portal booking example loses conversation after validation error
by Mauro Lopez (JIRA)
Portal booking example loses conversation after validation error
----------------------------------------------------------------
Key: JBSEAM-344
URL: http://jira.jboss.com/jira/browse/JBSEAM-344
Project: JBoss Seam
Issue Type: Bug
Components: Portal
Affects Versions: 1.0.1
Environment: JBoss 4.0.4.GA
JBoss Portal 2.4.0-Beta1
(used jems-installer-1.2.0.BETA)
JBoss Seam 1.0.1.GA
Reporter: Mauro Lopez
Followed this steps:
- deployed the application in examples/portal using ant, as described in examples/portal/readme.txt
- Entered http://localhost:8080/portal
- Selected the SeamHibernate portlet tab, registered user, logged in...
- Searched hotels, selected one of them, and pressed the "Book" button.
In the Book Hotel screen, if the credit card number hasn't got 16 digits, a message is shown. After that, having entered 16 digits for the credit card, instead of the confirm screen, the "Search Hotels" screen is shown, with the message "No conversation".
So, after a failed validation, the conversation is lost.
In my own examples I've substituted conversational scope with session scope, just to see them working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3603) 6 failing tests org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase (jrockit)
by Dimitris Andreadis (JIRA)
6 failing tests org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase (jrockit)
-----------------------------------------------------------------------------------
Key: JBAS-3603
URL: http://jira.jboss.com/jira/browse/JBAS-3603
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: JCA service, Test Suite
Reporter: Dimitris Andreadis
Assigned To: Weston Price
Fix For: JBossAS-4.0.5.GA
All but one org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase tests fail with
Transaction already active, cannot nest transactions.
javax.transaction.NotSupportedException: Transaction already active, cannot nest transactions.
at org.jboss.tm.TxManager.begin(TxManager.java:209)
at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.begin(ServerVMClientUserTransaction.java:124)
at org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase.testBrokenConnectionAndTrackByTx(XATxConnectionManagerUnitTestCase.java:290)
OR
Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=build01.dmz.inap.jboss.com/1, BranchQual=, localId=1])
org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=build01.dmz.inap.jboss.com/1, BranchQual=, localId=1])
at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:329)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnectManagedConnection(BaseConnectionManager2.java:518)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:399)
at org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase.testGetConnection(XATxConnectionManagerUnitTestCase.java:110)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
Caused by: javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=build01.dmz.inap.jboss.com/1, BranchQual=, localId=1]
at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener$TransactionSynchronization.checkEnlisted(TxConnectionManager.java:728)
at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.enlist(TxConnectionManager.java:561)
at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:323)
... 16 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3580) Error in org.jboss.test.jbossmq.test.UnackedUnitTestCase
by Dimitris Andreadis (JIRA)
Error in org.jboss.test.jbossmq.test.UnackedUnitTestCase
--------------------------------------------------------
Key: JBAS-3580
URL: http://jira.jboss.com/jira/browse/JBAS-3580
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JMS service, Test Suite
Environment: Java Version 1.4.2_09
Java Vendor Sun Microsystems Inc.
Java VM Name Java HotSpot(TM) Client VM
Java VM Version 1.4.2_09-b05
Java VM Info mixed mode
OS Name Linux
OS Version 2.6.9-34.0.2.ELsmp
OS Arch i386
Reporter: Dimitris Andreadis
Assigned To: Adrian Brock
Fix For: JBossAS-4.0.5.CR1
This seems like a clean-up problem of a previous test?
testUnackedDurableTopic
Error - The durable subscription is already in use. DurableSubscription[clientId=DurableSubscriberExample name=test selector=null]
javax.jms.IllegalStateException: The durable subscription is already in use. DurableSubscription[clientId=DurableSubscriberExample name=test selector=null]
at org.jboss.mq.server.JMSTopic.addSubscriber(JMSTopic.java:93)
at org.jboss.mq.server.ClientConsumer.addSubscription(ClientConsumer.java:142)
at org.jboss.mq.server.JMSDestinationManager.subscribe(JMSDestinationManager.java:572)
at org.jboss.mq.server.JMSServerInterceptorSupport.subscribe(JMSServerInterceptorSupport.java:171)
at org.jboss.mq.security.ServerSecurityInterceptor.subscribe(ServerSecurityInterceptor.java:157)
at org.jboss.mq.server.TracingInterceptor.subscribe(TracingInterceptor.java:643)
at org.jboss.mq.server.JMSServerInvoker.subscribe(JMSServerInvoker.java:177)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:185)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:534)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3492) Test Failure with JRockit: org.jboss.test.exception.EntityExceptionUnitTestCase
by Prabhat Jha (JIRA)
Test Failure with JRockit: org.jboss.test.exception.EntityExceptionUnitTestCase
-------------------------------------------------------------------------------
Key: JBAS-3492
URL: http://jira.jboss.com/jira/browse/JBAS-3492
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.0.5.CR1
Environment: linux - dev03 in qa lab, JRockit - java version "1.4.2_11"
Reporter: Prabhat Jha
Fix For: JBossAS-4.0.5.CR1
Six tests under org.jboss.test.exception.EntityExceptionUnitTestCase. All fail with the following error which can also be found at http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-1.4/20060....
Error, bean instance was discarded!
javax.ejb.FinderException: Error, bean instance was discarded!
at org.jboss.test.exception.EntityExceptionTesterBean.ejbFindByPrimaryKey(EntityExceptionTesterBean.java:59)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at org.jboss.ejb.plugins.BMPPersistenceManager.callFinderMethod(BMPPersistenceManager.java:632)
at org.jboss.ejb.plugins.BMPPersistenceManager.findEntity(BMPPersistenceManager.java:316)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:236)
at org.jboss.ejb.EntityContainer.findSingleObject(EntityContainer
On the server log, I see following for the first error in test suite.
2006-08-08 10:09:46,581 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/home/pjha/qa/405CR1/jboss405CR1/testsuite/output/lib/exception.jar
2006-08-08 10:09:47,003 DEBUG [org.jboss.ejb.StatelessSessionContainer] Useless invocation of remove() for stateless session bean
2006-08-08 10:09:47,150 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method: public abstract void org.jboss.test.exception.EntityExcepti\
onTesterLocal.runtimeExceptionNoTx():
java.lang.RuntimeException: Runtime exception without a transaction
at org.jboss.test.exception.EntityExceptionTesterBean.runtimeExceptionNoTx(EntityExceptionTesterBean.java:168)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1187)
at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:338)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentranceInterceptor.java:126)
at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:276)
at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:104)
at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:68)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:315)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:527)
at org.jboss.ejb.Container.invoke(Container.java:954)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months