[JBoss JIRA] Closed: (JBAS-40) naming.test.PooledInvokerUnitTestCase failures
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-40?page=all ]
Dimitris Andreadis closed JBAS-40.
----------------------------------
> naming.test.PooledInvokerUnitTestCase failures
> ----------------------------------------------
>
> Key: JBAS-40
> URL: http://jira.jboss.com/jira/browse/JBAS-40
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-3.2.7 Final
> Environment: [starksm@banshee9100 case2471]$ $JAVA_HOME/bin/java -version
> java version "1.3.1_14"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_14-b03)
> Java HotSpot(TM) Client VM (build 1.3.1_14-b03, mixed mode)
> Reporter: Scott M Stark
> Assigned To: Scott M Stark
> Fix For: JBossAS-3.2.7 Final
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> There are 2 similar failures in the org.jboss.test.naming.test.PooledInvokerUnitTestCase when running under jdk 1.3.1_14.
> <testcase classname="org.jboss.test.naming.test.PooledInvokerUnitTestCase" name="testCreateSubcontext" time="0.11">
> <error message="Operation failed" type="javax.naming.CommunicationException">javax.naming.CommunicationException: Operation failed. Root exception is java.net.BindException: Cannot assign requested address: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
> at java.net.Socket.<init>(Socket.java:268)
> at java.net.Socket.<init>(Socket.java:95)
> at org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.getConnection(PooledInvokerProxy.java:236)
> at org.jboss.invocation.pooled.interfaces.PooledInvokerProxy.invoke(PooledInvokerProxy.java:322)
> at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:96)
> at org.jboss.naming.interceptors.ExceptionInterceptor.invoke(ExceptionInterceptor.java:42)
> at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
> at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:55)
> at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:91)
> at $Proxy1.createSubcontext(Unknown Source)
> at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:876)
> at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:858)
> at javax.naming.InitialContext.createSubcontext(InitialContext.java:411)
> at org.jboss.test.naming.test.PooledInvokerUnitTestCase.testCreateSubcontext(PooledInvokerUnitTestCase.java:51)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> </error>
> </testcase>
--
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, 3 months
[JBoss JIRA] Closed: (JBAS-37) Cache test failures under jdk1.3
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-37?page=all ]
Dimitris Andreadis closed JBAS-37.
----------------------------------
> Cache test failures under jdk1.3
> --------------------------------
>
> Key: JBAS-37
> URL: http://jira.jboss.com/jira/browse/JBAS-37
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JBoss Cache
> Affects Versions: JBossAS-3.2.7 Final
> Environment: [starksm@banshee9100 testsuite]$ $JAVA_HOME/bin/java -version
> java version "1.3.1_14"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_14-b03)
> Java HotSpot(TM) Client VM (build 1.3.1_14-b03, mixed mode)
> Reporter: Scott M Stark
> Assigned To: Ben Wang
> Priority: Blocker
> Fix For: JBossAS-3.2.7 Final
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> There are some cache unit test failures when running under jdk1.3 that need to be resolved:
> [junit] Running org.jboss.test.cache.test.local.TxConcurrentUnitTestCase
> [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
> [junit] Test org.jboss.test.cache.test.local.TxConcurrentUnitTestCase FAILED (timeout)
> [junit] Running org.jboss.test.classloader.test.BasicLoaderUnitTestCase
> [junit] Tests run: 4, Failures: 0, Errors: 1, Time elapsed: 12.469 sec
> [junit] Test org.jboss.test.classloader.test.BasicLoaderUnitTestCase FAILED
> The 3.2 codebase needs to be synched with the jboss-head cache source as a starting point.
--
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, 3 months
[JBoss JIRA] Closed: (JBAS-38) cmp2.commerce.CompleteUnitTestCase error
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-38?page=all ]
Dimitris Andreadis closed JBAS-38.
----------------------------------
> cmp2.commerce.CompleteUnitTestCase error
> ----------------------------------------
>
> Key: JBAS-38
> URL: http://jira.jboss.com/jira/browse/JBAS-38
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-3.2.7 Final
> Environment: [starksm@banshee9100 case2471]$ $JAVA_HOME/bin/java -version
> java version "1.3.1_14"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_14-b03)
> Java HotSpot(TM) Client VM (build 1.3.1_14-b03, mixed mode)
> Reporter: Scott M Stark
> Assigned To: Alexey Loubyansky
> Fix For: JBossAS-3.2.7 Final
>
>
> There is one failure in org.jboss.test.cmp2.commerce.CompleteUnitTestCase when running the current 3.2 codebase with both the server and testsuite compiled with jdk 1.3.1_14.
> <testcase classname="org.jboss.test.cmp2.commerce.QueryTest" name="testEJBQL" time="0.031">
> <failure message="expected:<...0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER AND t6_
> l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_produ
> ct_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productC
> ategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id> but was:
> <...6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t
> 5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product
> _productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id AND
> t0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER>" type="net.sourceforge.junitejb.RemoteA
> ssertionFailedError">junit.framework.ComparisonFailure: expected:<...0_o.ORDE
> R_NUMBER=t4_l.ORDER_NUMBER AND t6_l_product.id=t5_l_product_productCategories_R.
> PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND
> t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.pr
> oduct=t6_l_product.id> but was:<...6_l_product.id=t5_l_product_productCate
> gories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGO
> RY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AN
> D t4_l.product=t6_l_product.id AND t0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER>
> at org.jboss.test.cmp2.commerce.QueryTest.testEJBQL(QueryTest.java:307)
> at net.sourceforge.junitejb.EJBTestCase.runBare(EJBTestCase.java:133)
> at net.sourceforge.junitejb.EJBTestRunnerBean.runTestCase(EJBTestRunnerBean.java:102)
--
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, 3 months
[JBoss JIRA] Closed: (JBAS-30) txtimers created via Servlet init get duplicated.
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-30?page=all ]
Dimitris Andreadis closed JBAS-30.
----------------------------------
> txtimers created via Servlet init get duplicated.
> -------------------------------------------------
>
> Key: JBAS-30
> URL: http://jira.jboss.com/jira/browse/JBAS-30
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-4.0.1 Final
> Environment: jboss-4.0.1RC2
> Reporter: Phil Cornelius
> Assigned To: Scott M Stark
> Fix For: JBossAS-4.0.1 Final
>
>
> I have a stateless SessionBean that is also a
> javax.ejb.TimedObject.
> I set the timer running by calling a 'schedule'
> business method
> public void schedule(int mins) {
> TimerService timerService = mySessionCtx.getTimerService();
> // Now and every mins minutes
> timerService.createTimer(0L, 60000L * mins, "iPML export timer.");
> }
> This methods gets called from the init method of a
> Servlet.. everything works except that two timers get
> created.. the second about 20 seconds after the first..
> I have tracked it down to the following problem.. but
> am not sure how to solve it.
> 1. The timer gets created and a row is written into the
> localDB hypersonic database.
> 2. Once jboss is started (approx 20 seconds after the
> init method of my servlet was called) a notification is
> sent to org.jboss.ejb.txtimer.DatabasePersistencePolicy
> line 102
> where the method
> restoreTimers();
> is called
> 3. This method reads the row in hsqldb and creates
> another duplicate txtimer
> The other thing that I noticed was that the instance
> variable 'instancePk' of the class
> org.jboss.ejb.txtimer.TimedObjectId never gets assigned
> any value.
> This bug is against jboss-4.0.1RC2
> Yours
> Phil
--
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, 3 months
[JBoss JIRA] Closed: (JBAS-21) Cannot find wsdl in client deployment
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-21?page=all ]
Dimitris Andreadis closed JBAS-21.
----------------------------------
> Cannot find wsdl in client deployment
> -------------------------------------
>
> Key: JBAS-21
> URL: http://jira.jboss.com/jira/browse/JBAS-21
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Priority: Trivial
> Fix For: JBossAS-4.0.2 Final
>
>
> The <wsdl-file> was not null in this case but pointed to WEB-INF which did not exist
> Caused by: java.lang.IllegalArgumentException: WSDL file argument cannot be null
> at org.jboss.webservice.WSDLDefinitionFactory$WSDLLocatorImpl.<init>(WSDLDefinitionFactory.java:95)
> at org.jboss.webservice.WSDLDefinitionFactory.parse(WSDLDefinitionFactory.java:58)
> at org.jboss.metadata.ServiceRefMetaData.getWsdlDefinition(ServiceRefMetaData.java:170)
> at org.jboss.webservice.ServiceClientDeployer.setupServiceRefEnvironment(ServiceClientDeployer.java:63)
> ... 30 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, 3 months
[JBoss JIRA] Closed: (JBAS-14) CompleteUnitTestCase fails under java5
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-14?page=all ]
Dimitris Andreadis closed JBAS-14.
----------------------------------
> CompleteUnitTestCase fails under java5
> --------------------------------------
>
> Key: JBAS-14
> URL: http://jira.jboss.com/jira/browse/JBAS-14
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-4.0.1 Final
> Environment: 13:35:08,406 INFO [Server] Starting JBoss (MX MicroKernel)...
> 13:35:08,406 INFO [Server] Release ID: JBoss [Zion] 4.0.1RC2 (build: CVSTag=Branch_4_0 date=200411271821)
> 13:35:08,406 INFO [Server] Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2
> 13:35:08,406 INFO [Server] Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/
> 13:35:08,406 INFO [Server] Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/lib/
> 13:35:08,406 INFO [Server] Patch URL: null
> 13:35:08,406 INFO [Server] Server Name: all
> 13:35:08,406 INFO [Server] Server Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all
> 13:35:08,421 INFO [Server] Server Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/
> 13:35:08,421 INFO [Server] Server Data Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\data
> 13:35:08,421 INFO [Server] Server Temp Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\tmp
> 13:35:08,421 INFO [Server] Server Config URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/conf/
> 13:35:08,421 INFO [Server] Server Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/lib/
> 13:35:08,421 INFO [Server] Root Deployment Filename: jboss-service.xml
> 13:35:08,421 INFO [Server] Starting General Purpose Architecture (GPA)...
> 13:35:08,937 INFO [ServerInfo] Java version: 1.5.0,Sun Microsystems Inc.
> 13:35:08,937 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Sun Microsystems Inc.
> 13:35:08,937 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
> Reporter: Scott M Stark
> Assigned To: Alexey Loubyansky
> Fix For: JBossAS-4.0.1 Final
>
>
> When running the org.jboss.test.cmp2.commerce.CompleteUnitTestCase test under java5 there are two failures related to query expecation failures:
> Suite: org.jboss.test.cmp2.commerce.CompleteUnitTestCase
> Test: testJBossQL
> Type: failure
> Exception: net.sourceforge.junitejb.RemoteAssertionFailedError
> Message: Expected: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t1_o1_customer, CUSTOMEREJB t2_o2_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t0_o1.customer=t1_o1_customer.id AND t3_o2.customer=t2_o2_customer.id) but got: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t2_o2_customer, CUSTOMEREJB t1_o1_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t3_o2.customer=t2_o2_customer.id AND t0_o1.customer=t1_o1_customer.id)
> ---------------------------------
> Suite: org.jboss.test.cmp2.commerce.CompleteUnitTestCase
> Test: testEJBQL
> Type: failure
> Exception: net.sourceforge.junitejb.RemoteAssertionFailedError
> Message: expected:<...0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER AND t6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id> but was:<...6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id AND t0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER>
> ---------------------------------
--
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, 3 months
[JBoss JIRA] Closed: (JBAS-15) ContextCLTestCase fails under java5
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-15?page=all ]
Dimitris Andreadis closed JBAS-15.
----------------------------------
> ContextCLTestCase fails under java5
> -----------------------------------
>
> Key: JBAS-15
> URL: http://jira.jboss.com/jira/browse/JBAS-15
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-4.0.1 Final
> Environment: java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
> Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode)
> Reporter: Scott M Stark
> Assigned To: Scott M Stark
> Fix For: JBossAS-4.0.1 Final
>
>
> org.jboss.test.jbossmx.implementation.server.ContextCLTestCase is failing when run under java5:
> Suite: org.jboss.test.jbossmx.implementation.server.ContextCLTestCase
> Test: testInvokeNeedingTCL
> Type: error
> Exception: javax.management.ReflectionException
> Message: The MBean class could not be loaded by the default loader repository
--
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, 3 months