April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-17) jpdl designer user guide and documentation

by Koen Aers (JIRA)

jpdl designer user guide and documentation ------------------------------------------ Key: GPD-17 URL: http://jira.jboss.com/jira/browse/GPD-17 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers A new user guide using screenshots of the new product should be written. -- 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

14 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCOMMON-35) NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .

by Vicky Kak (JIRA)

NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock . ------------------------------------------------------------------------------ Key: JBCOMMON-35 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-old Affects Versions: 1.0.0.GA Reporter: Vicky Kak Assigned To: Vicky Kak Fix For: 2.2.2.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA http://forum.java.sun.com/thread.jspa?threadID=752201 -- 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

14 years, 11 months

2
15
0 / 0

[JBoss JIRA] Created: (JBAS-4595) Inconclusive exception thrown by HttpNamingContextFactory

by Carlo de Wolf (JIRA)

Inconclusive exception thrown by HttpNamingContextFactory --------------------------------------------------------- Key: JBAS-4595 URL: http://jira.jboss.com/jira/browse/JBAS-4595 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Environment: Hudson only Sun VM 1.5.0_12-b04 Ubuntu 6.06 Reporter: Carlo de Wolf Priority: Minor Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA javax.naming.NamingException: Failed to retrieve Naming interface [Root exception is java.net.ConnectException: Connection refused] at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:84) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at org.jboss.ejb3.test.invoker.unit.InvokerTestCase.testHttp(InvokerTestCase.java:55) 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) Caused by: java.net.ConnectException: Connection refused at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1223) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1217) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:906) at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:133) at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:80) ... 26 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:382) at sun.net.www.http.HttpClient.openServer(HttpClient.java:509) at sun.net.www.http.HttpClient.<init>(HttpClient.java:231) at sun.net.www.http.HttpClient.New(HttpClient.java:304) at sun.net.www.http.HttpClient.New(HttpClient.java:316) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:1903) at java.net.URLConnection.getHeaderFieldInt(URLConnection.java:573) at java.net.URLConnection.getContentLength(URLConnection.java:468) at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:128) ... 27 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1894) Portlet instances cannot be deleted with the GUI after undeployment

by Martin Putz (JIRA)

Portlet instances cannot be deleted with the GUI after undeployment ------------------------------------------------------------------- Key: JBPORTAL-1894 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1894 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.3 Final Reporter: Martin Putz Assigned To: Thomas Heute When a portlet application (*.war) is undeployed, the portlet instances defined in portlet-instances.xml remain in the JBP_INSTANCE table. This causes problems if the same application is redeployed under a different context name. The instances are also not listed in the management portlet GUI, which would allow to delete them manually. -- 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

14 years, 12 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3521) OptimisticLockUnitTestCase Intermittently Fails

by Matt Wringe (JIRA)

OptimisticLockUnitTestCase Intermittently Fails ----------------------------------------------- Key: JBAS-3521 URL: http://jira.jboss.com/jira/browse/JBAS-3521 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: Sun 1.4.2_12 JVM RHEL 4, Linux Kernel 2.6.9 Reporter: Matt Wringe The OptimisticLockUnitTestCase testBug1006723 test seems to fail randomly. This is a known issue, and is described here: http://wiki.jboss.org/wiki/Wiki.jsp?page=TestsuiteTroubleShooting But there does not appear to be a bug filed about this issue, nor can I find bug 1006723 "Problem OptimisticLockUnitTestCase fails Suite: org.jboss.test.cmp2.optimisticlock.test.OptimisticLockUnitTestCase Test: testBug1006723 Type: error Exception: javax.ejb.CreateException Message: Error checking if entity exists:java.sql.SQLException: Column not found: \ OIDCMP in statement SELECT COUNT(*) FROM ENTITYA WHERE OIDCMP=? This test passes intermintently. Run it a few times" -- 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

14 years, 12 months

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-4598) TimerHandle failed to retrieve timer after JBoss restart

by Linoux Linoux (JIRA)

TimerHandle failed to retrieve timer after JBoss restart -------------------------------------------------------- Key: JBAS-4598 URL: http://jira.jboss.com/jira/browse/JBAS-4598 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: Windows XP / PostgreSQL Reporter: Linoux Linoux Creating a timer, store the associated TimerHandle in DB. Restart JBoss server, try to get the Timer using the stored TimerHandle : javax.ejb.NoSuchObjectLocalException is thrown. ---------------------------------------------------------- //In a Stateless Session : @TransactionAttribute(TransactionAttributeType.REQUIRED) public void createTimer() throws OgpException { TimerService ts = ctx.getTimerService(); Timer newTimer = ts.createTimer(getTimerStartDate(), DateUtil.MILLIS_IN_DAY, testAge); conf.setTestCleanTimerHandle(newTimer.getHandle()); // Store conf in DB } private Timer getCurrentTimer(DbConfiguration conf) throws OgpException { if (conf.getTestCleanTimerHandle() == null) return null; try { return conf.getTestCleanTimerHandle().getTimer(); } catch (NoSuchObjectLocalException e) { log.warn("Can't retrieve timer : it could be caused by the application redeployment", e); return null; } } ---------------------------------------------------------- Using this code, call to getCurrentTimer after calling createTimer works fine, but after a JBoss restart, call to getCurrentTimer ends with a NoSuchObjectLocalException : javax.ejb.NoSuchObjectLocalException: Timer not available: [target=jboss.j2ee:service=EJB3,ear=ogp-app.ear,jar=ogp-ejb.jar,name=AdminCleanDbSessionBean] at org.jboss.ejb.txtimer.TimerHandleImpl.getTimer(TimerHandleImpl.java:203) at com.sts.ogp.ejb.admin.AdminCleanDbSessionBean.getCurrentTimer(AdminCleanDbSessionBean.java:157) [...] -- 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

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1262) DSL Parser "eval"

by M H (JIRA)

DSL Parser "eval" ----------------- Key: JBRULES-1262 URL: http://jira.jboss.com/jira/browse/JBRULES-1262 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Reporter: M H Assigned To: Mark Proctor [when]of type Item=Item() [when]- Title equals "{value}"=eval(title.isEqual("{value}") [when]- Event equals "{value}"=eval(id.isEqual("{value}") [then]Log : "{message}"=System.out.println("{message}"); the dslr File: expander Test.dsl rule "Your First Rule" when $p : of type Item - Title equals "test" - Event equals "test" then #actions end resolves to (could be seen in the drl viewer) rule "Your First Rule" when $p :Item( eval(title.isEqual("test", eval(id.isEqual("test") ) ) then #actions end -- 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

15 years

5
18
0 / 0

[JBoss JIRA] Created: (JBAS-4043) Allow webapps for different tomcat services to deployed in the same .ear

by Martin Welss (JIRA)

Allow webapps for different tomcat services to deployed in the same .ear ------------------------------------------------------------------------ Key: JBAS-4043 URL: http://jira.jboss.com/jira/browse/JBAS-4043 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.5.GA Environment: jboss with embedded tomcat configured with 2 services, like in JBAS-2410 Reporter: Martin Welss Assigned To: Dimitris Andreadis The second tomcat service has its own deployment directory, so the deployment has to be splitted into two separate files. This causes timing problems (NoClassDefFoundError), because our ejb3 application takes amch longer to deploy than our webapp. Maybe a new tag in jbossweb.xml could target the webapp to the respective tomcat-service -- 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

15 years

2
5
0 / 0

[JBoss JIRA] Created: (JBWEB-101) Thread handle leak using Jboss Web native connectors on Windows

by Mike Poindexter (JIRA)

Thread handle leak using Jboss Web native connectors on Windows --------------------------------------------------------------- Key: JBWEB-101 URL: http://jira.jboss.com/jira/browse/JBWEB-101 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.1 GA Reporter: Mike Poindexter Assigned To: Mladen Turk When running JBossWeb using the native connectors under Windows XP/Win2k3 I'm seeing a Thread Handles leak. I've traced this with the !htrace feature of CDB (like at http://blogs.technet.com/brad_rutkowski/archive/2007/11/13/got-a-handle-l...). It appears as though this is the behavior reported at https://issues.apache.org/bugzilla/show_bug.cgi?id=42728. The native stack trace from the leaked handles looks like: Handle = 0x00000c64 - OPEN Thread ID = 0x00001014, Process ID = 0x00003e44 0x2c2d624c: libapr_1!apr_os_thread_current+0x0000003c 0x2c339202: LIBEAY32!ERR_remove_state+0x00000062 0x7c9011a7: ntdll!LdrInitializeThunk+0x00000029 0x7c919213: ntdll!LdrShutdownThread+0x000000ed 0x7c80c096: kernel32!ExitThread+0x0000003e 0x7c87545b: kernel32!GetConsoleCharType+0x000002a8 0x7c80b683: kernel32!GetModuleFileNameA+0x000001b4 >From what I can tell, the end result is that one thread handle leaks per JVM thread that terminates. Over the course of a long running server application, this becomes a major leak. -- 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

15 years

3
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-978) Deployer should ignore files that Javassist throws a "non class file" exception for

by Josh Devins (JIRA)

Deployer should ignore files that Javassist throws a "non class file" exception for ----------------------------------------------------------------------------------- Key: EJBTHREE-978 URL: http://jira.jboss.com/jira/browse/EJBTHREE-978 Project: EJB 3.0 Issue Type: Bug Environment: JBoss 4.0.5 GA with EJB3 deployer and IBM DB2 JDBC driver v3.3.54 Reporter: Josh Devins This is a follow-up to a Javassist issue # JASSIST-34. For some reason, the IBM DB2 JDBC jar file contains a class that does not start with the magic code "0xCAFEBABE". When the EJB3 deployer looks at this jar file and scans the classes in it, Javassist is throwing an IOException with message "non class file". This is entirely useless to the end user since there is no information given about what class file or jar file is in error. Javassist should be throwing a more descriptive exception (as per the issue JASSIST-34), and the EJB3 deployer should simply skip that file and output a warning telling the user/developer what jar file and class was in error. -- 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

15 years, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008