January 2007 - jboss-jira - Jboss List Archives

by fvd

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-836) Quartz Resourceadapter: Quartz with JDBC-Jobstore (required for Clustering) leads to NPE in QuartzJob

by Dieter Rehbein (JIRA)

Quartz Resourceadapter: Quartz with JDBC-Jobstore (required for Clustering) leads to NPE in QuartzJob ----------------------------------------------------------------------------------------------------- Key: EJBTHREE-836 URL: http://jira.jboss.com/jira/browse/EJBTHREE-836 Project: EJB 3.0 Issue Type: Bug Reporter: Dieter Rehbein Attachments: ejb3tests.jar, quartz-ds.xml, quartz.properties For our customer we need clustered quartz-timers. This requires a JDBC-Jobstore (see http://wiki.opensymphony.com/display/QRTZ1/TutorialLesson11). Using a JDBC-Jobstore leads to the following exception: 16:46:40,046 ERROR [JobRunShell] Job default.job.0.1169048021109 threw an unhandled Exception: java.lang.NullPointerException at org.jboss.resource.adapter.quartz.inflow.QuartzJob.execute(QuartzJob.java:53) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) This is what we've done: 1. installed jBoss with ejb3 clustered profile 2. created a quartz.properties in directory <jboss-home>/server/default/conf (see attached file) 3. added a quartz-ds.xml to <jboss-home>/server/default/deploy (using a mySQL-database) (see attached file) 4. moved the file quartz-ra.rar from <jboss-home>/server/default/deploy to <jboss-home>/server/default/deploy/deploy.last (to ensure, that the JDBC-datasource is already bound to JNDI when the resource-adapater is deployed) 5. created a simple test MDB (see attached files TestJob.java and ejb3test.jar) and deployed it to directory <jboss-home>/server/default/deploy/deploy.last 6. started jBoss => you can see the NPE every 10 seconds I've debugged a little bit. This is, what I've found so far: * If a JobStoreTX is used as JobStore, the class JobStoreTX uses StdJDBCDelegate.insertJobDetail(..) to store the JobDetails in the database. The method insertJobDetail(...) serializes the JobDataMap into a ByteArrayOutputStream. The method endpointActivation(..) of class org.jboss.resource.adapter.quartz.inflow.QuartzResourceAdapter adds a reference to the MessageEndpointFactory to the JobDataMap (using the key "endpointFactory"). Since the MessageEndpointFactory is not serializable, the MessageEndpointFactory is not stored in the JDBC-Jobstore ! * The method execute(...) of org.jboss.resource.adapter.quartz.inflow.QuartzJob retrieves the "endpointFactory" from the JobDataMap (which returns null, because it was not serialized). In line 53 the method createEndpoint(..) is called on a null-object => NPE -- 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

1
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-749) Connection Timeouts that can lead to Serialization Exceptions

by Clebert Suconic (JIRA)

Connection Timeouts that can lead to Serialization Exceptions ------------------------------------------------------------- Key: JBMESSAGING-749 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-749 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP2 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.0.1.SP3 -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3615) failing test in org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase

by Dimitris Andreadis (JIRA)

failing test in org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase ------------------------------------------------------------------------------ Key: JBAS-3615 URL: http://jira.jboss.com/jira/browse/JBAS-3615 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX, Test Suite Environment: Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_05-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: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA testMalformed Failure invalid object name: domain:=,foo=bar junit.framework.AssertionFailedError: invalid object name: domain:=,foo=bar at org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase$FullNameTEST.testMalformed(MalformedTestCase.java:152) -- 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

2
16
0 / 0

[JBoss JIRA] Created: (JBREM-670) Remove equals() and hashCode() from org.jboss.remoting.transport.rmi.RemotingRMIClientSocketFactory.

by Ron Sigal (JIRA)

Remove equals() and hashCode() from org.jboss.remoting.transport.rmi.RemotingRMIClientSocketFactory. ---------------------------------------------------------------------------------------------------- Key: JBREM-670 URL: http://jira.jboss.com/jira/browse/JBREM-670 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) The definition of hashCode is problematic because it depends on the presence or absence of a SocketFactory, which comes and goes during createSocket(). Currently, the RemotingRMIClientSocketFactory is used as a key in a HashMap, and the SocketFactory is present when the entry is made and absent when the table is later searched. The result is that a new SocketFactory is created during each call to createSocket(). -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-669) Client.removeListener() should catch exception and continue if invocation to server fails.

by Ron Sigal (JIRA)

Client.removeListener() should catch exception and continue if invocation to server fails. ------------------------------------------------------------------------------------------ Key: JBREM-669 URL: http://jira.jboss.com/jira/browse/JBREM-669 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) If a server goes down, Client.removeListener() might get an exception when trying to contact the server, which will prevent it from finishing the process of removing the callback handler on the client side. -- 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

1
1
0 / 0

[JBoss JIRA] Resolved: (JBAS-3978) One off patch for ASPATCH-137: JConsole throws exception on connect post

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3978?page=all ] Ryan Campbell resolved JBAS-3978. --------------------------------- Assignee: JBN Patch Team (was: Pavel Tsekov) > One off patch for ASPATCH-137: JConsole throws exception on connect post > ------------------------------------------------------------------------- > > Key: JBAS-3978 > URL: http://jira.jboss.com/jira/browse/JBAS-3978 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.5.GA > Reporter: Scott M Stark > Assigned To: JBN Patch Team > Attachments: jboss-system.jar, run.jar, TESTS-patched.FIRST.RUN.txt > > Original Estimate: 1 hour > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Need a one off patch for the ASPATCH-137(jconsole issue) since 4.0.5CP1 did not go out. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-695) Have the GPD add all default attributes to nodes instead of leaving them out

by Ronald van Kuijk (JIRA)

Have the GPD add all default attributes to nodes instead of leaving them out ---------------------------------------------------------------------------- Key: JBPM-695 URL: http://jira.jboss.com/jira/browse/JBPM-695 Project: JBoss jBPM Issue Type: Feature Request Components: Graphical Process Designer Environment: N/A Reporter: Ronald van Kuijk Assigned To: Tom Baeyens It would be nice if the GPD added the defaults of attributes to nodes (e.g. task-end="false" on a tasknode) this way, even with no graphical support, users often think further, search for it etc, that it would help (even for me!!! ;-)) -- 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

2
5
0 / 0

[JBoss JIRA] Commented: (JBAS-3978) One off patch for ASPATCH-137: JConsole throws exception on connect post

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3978?page=comments#action_12351077 ] Ryan Campbell commented on JBAS-3978: ------------------------------------- Agreed, all three are not regressions. > One off patch for ASPATCH-137: JConsole throws exception on connect post > ------------------------------------------------------------------------- > > Key: JBAS-3978 > URL: http://jira.jboss.com/jira/browse/JBAS-3978 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.5.GA > Reporter: Scott M Stark > Assigned To: Pavel Tsekov > Attachments: jboss-system.jar, run.jar, TESTS-patched.FIRST.RUN.txt > > Original Estimate: 1 hour > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Need a one off patch for the ASPATCH-137(jconsole issue) since 4.0.5CP1 did not go out. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-302) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: JBAOP-302 URL: http://jira.jboss.com/jira/browse/JBAOP-302 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Fix For: 1.5.3.GA, 2.0.0.alpha2 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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

2
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007