[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, 10 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, 10 months
[JBoss JIRA] Created: (JBAS-3496) all tests under org.jboss.test.cmp2.cmrtree.test fail with javax.ejb.DuplicateKeyException
by Prabhat Jha (JIRA)
all tests under org.jboss.test.cmp2.cmrtree.test fail with javax.ejb.DuplicateKeyException
------------------------------------------------------------------------------------------
Key: JBAS-3496
URL: http://jira.jboss.com/jira/browse/JBAS-3496
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CMP service, Test Suite
Affects Versions: JBossAS-4.0.5.CR1
Environment: linux -dev03 in qa, JRockit 1.4.2.11
Reporter: Prabhat Jha
Assigned To: Alexey Loubyansky
Fix For: JBossAS-4.0.5.CR1
This error does not happen with Sun JDK1.4.
All test cases under org.jboss.test.cmp2.cmrtree.test have following error:
Entity with primary key [.1.A.] already exists
javax.ejb.DuplicateKeyException: Entity with primary key [.1.A.] already exists
at org.jboss.ejb.plugins.cmp.jdbc.JDBCInsertPKCreateCommand.beforeInsert(JDBCInsertPKCreateCommand.java:99)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractCreateCommand.execute(JDBCAbstractCreateCommand.java:150)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.createEntity(JDBCStoreManager.java:587)
at org.jboss.ejb.plugins.CMPPersistenceManager.createEntity(CMPPersistenceManager.java:237)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.createEntity(CachedConnectionInterceptor.java:225)
at org.jboss.ejb.EntityContainer.createLocalHome(EntityContainer.java:625)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1126)
at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:105)
at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:203)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:189)
at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:105)
at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:134)
at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:76)
at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:43)
at org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:56)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:125)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:161)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:145)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)
at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:521)
at org.jboss.ejb.Container.invoke(Container.java:975)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:359)
at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:133)
at $Proxy204.create(ILjava.lang.String;Ljava.lang.String;)Lorg.jboss.test.cmp2.cmrtree.ejb.ALocal;(Unknown Source)
--
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, 10 months
[JBoss JIRA] Created: (JBAS-3497) All tests (21) under org.jboss.test.cmp2.lob fail with javax.ejb.ObjectNotFoundException
by Prabhat Jha (JIRA)
All tests (21) under org.jboss.test.cmp2.lob fail with javax.ejb.ObjectNotFoundException
----------------------------------------------------------------------------------------
Key: JBAS-3497
URL: http://jira.jboss.com/jira/browse/JBAS-3497
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CMP service, Test Suite
Affects Versions: JBossAS-4.0.5.CR1
Environment: linux - dev03 in qa, java: Jrockit 1.4.2.11
Reporter: Prabhat Jha
Assigned To: Alexey Loubyansky
Fix For: JBossAS-4.0.5.CR1
All tests under org.jboss.test.cmp2.lob fail with javax.ejb.ObjectNotFoundException. Here is the complete error log:
No such entity!
javax.ejb.ObjectNotFoundException: No such entity!
at org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute(JDBCFindEntityCommand.java:64)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDBCStoreManager.java:604)
at org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPersistenceManager.java:315)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:236)
at org.jboss.ejb.EntityContainer.findSingleObject(EntityContainer.java:1099)
at org.jboss.ejb.EntityContainer.find(EntityContainer.java:728)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1126)
at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:105)
at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:203)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:189)
at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:105)
at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:134)
at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:76)
at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:43)
at org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:56)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:125)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:161)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:145)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)
at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:521)
at org.jboss.ejb.Container.invoke(Container.java:975)
Complete error log can be found at http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-1.4/20060....
--
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, 10 months
[JBoss JIRA] Created: (JBSEAM-340) Streamline use of i18n validation error messages
by Manfred Moser (JIRA)
Streamline use of i18n validation error messages
-------------------------------------------------
Key: JBSEAM-340
URL: http://jira.jboss.com/jira/browse/JBSEAM-340
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.0.1
Environment: Seam 1.0.1.GA
Reporter: Manfred Moser
As described in the forum post referenced introducing i18n error message from validation of an entity bean does not have an example anywhere and actually only works nicely with a bit of a work around. The situation is that the hibernate validation needs the error message in ValidatorMessages_*.properties and Seam has its properties in messages_*.properties. For the entity bean to work without Seam (e.g. in a unit test that verifies the validation settings) the messages have to exist in the hibnerate resource bundle. For usage in Seam they have to exist in the Seam bundle. For a Seam app to actually start up all properties related to exist in the Hibnerate and the Seam bundles .. which leads to ugly duplication. A fix is to keep all properties in the seam bundles and copy them into the hibernate bundle at build time. The forum post has a ant task. It would however be better if Seam could somehow manage to pass the resources to hibernate or otherwise just automatically include the hibernate bundle. An example of the i18n of the validation message and other annotation based messages should be included in the examples.
--
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, 10 months
[JBoss JIRA] Created: (JBSEAM-336) BigDecimal is not handled properly
by Valerij Timofeev (JIRA)
BigDecimal is not handled properly
----------------------------------
Key: JBSEAM-336
URL: http://jira.jboss.com/jira/browse/JBSEAM-336
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.0.1
Environment: German or US locale, Windows XP Pro, myfaces 1.1.3, Oracle 9.2 or MySQL 4.1.9
Reporter: Valerij Timofeev
Generating CRUD Seam applications results in some fields having Java type BigDecimal.
It seems that this type is not handled properly.
There are no error messages in the JBoss server.log (log4j javax.faces & org.jboss.seam priorities are DEBUG). Query returns no results.
Debugging shows for example that findFirstPage() method is never called.
Changing type e.g. to Double fixes the issue (see workarounds for details) : it becomes possible to step through the method. And query returns some results.
Clicking on create link and then switching to find view (other bean than current) results in the following JSF error:
Cannot set value for expression '#{somebeanEditor.instance.id}' to a new value of type java.lang.String
Where ID is of type BigDecimal.
--
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, 10 months