September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-419) Enable module unit tests for app server builds

by Paul Gier (JIRA)

Enable module unit tests for app server builds ---------------------------------------------- Key: JBBUILD-419 URL: http://jira.jboss.com/jira/browse/JBBUILD-419 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Several app server modules contain unit tests. Test scope dependencies should be added to the poms for these tests, and the tests should be enabled with the surefire plugin. -- 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

16 years, 11 months

1
8
0 / 0

[JBoss JIRA] Created: (BPEL-244) Support for BPEL process instance monitoring in jBPM admin console

by Meghana Joglekar (JIRA)

Support for BPEL process instance monitoring in jBPM admin console ------------------------------------------------------------------ Key: BPEL-244 URL: http://jira.jboss.com/jira/browse/BPEL-244 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Reporter: Meghana Joglekar Assigned To: Alejandro Guizar One can currently run BPEL processes on jBPM engine and check the log files to see the runtime report. But this process is not efficient in monitoring how the process is doing, what processes are running, what went wrong when a fault occurred etc. It will be nice to have administration console to see this information. The administration console can then list the process instances that are running, show visual graph of the instance and for each node in the graph more information about it. ActiveBPEL and OracleBPEL both provide such consoles and they are great tools for administrators. It will be nice if it also provides 'delete' functionality for stalled processes or old processes. The list could go on but in its basic form, processes listing, process instance listing and then more information about them [instances] will be useful. -- 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

16 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-759) CLONE -Unable to add package after it was added and removed

by Brugger Antony (JIRA)

CLONE -Unable to add package after it was added and removed ----------------------------------------------------------- Key: JBRULES-759 URL: http://jira.jboss.com/jira/browse/JBRULES-759 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.4 Environment: Windows2000 Advanced Server JBRules3.0.4 Reporter: Brugger Antony Assigned To: Edson Tirelli Fix For: 3.0.5 Unable remove a rule package when it was added after it has been added and removed. I have seen the issue [#JBRULES-358]. My test go a little far than [#JBRULES-358]. I remove the package again when it was added for the seconn time, then an exception was thrown. My test case is: public void testRuleBaseRemove() throws Exception { RuleBase ruleBase = RuleBaseFactory.newRuleBase(); File file = new File("test.drl"); //add and remove PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl(new FileReader(file)); Package pkg = builder.getPackage(); ruleBase.addPackage(pkg); ruleBase.removePackage(pkg.getName()); //add and remove again builder = new PackageBuilder(); builder.addPackageFromDrl(new FileReader(file)); pkg = builder.getPackage(); ruleBase.addPackage(pkg); ruleBase.removePackage(pkg.getName()); } the exception is throw: java.lang.NullPointerException at org.drools.reteoo.HashedObjectSinkList.remove(HashedObjectSinkList.java:102) at org.drools.reteoo.ObjectTypeNode.remove(ObjectTypeNode.java:245) at org.drools.reteoo.AlphaNode.remove(AlphaNode.java:211) at org.drools.reteoo.AlphaNode.remove(AlphaNode.java:211) at org.drools.reteoo.LeftInputAdapterNode.remove(LeftInputAdapterNode.java:285) at org.drools.reteoo.TerminalNode.remove(TerminalNode.java:297) at org.drools.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:589) at org.drools.reteoo.ReteooRuleBase.removeRule(ReteooRuleBase.java:244) at org.drools.common.AbstractRuleBase.removePackage(AbstractRuleBase.java:338) at com.zte.ums.uep.pal.fm.osf.rules.core.RuleBaseTest.testRuleBaseRemove(RuleBaseTest.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- 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

16 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-912) ejb-jar.xml injected EntityManger fails in @PostConstruct annotated methods

by Andrew Redhead (JIRA)

ejb-jar.xml injected EntityManger fails in @PostConstruct annotated methods --------------------------------------------------------------------------- Key: EJBTHREE-912 URL: http://jira.jboss.com/jira/browse/EJBTHREE-912 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: Identified on jboss-4.0.5.GA from jems installer 1.2.GA, still present in head from svn co http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_0/ as of 13th March 2007. Tests run agains JDK 1.5 on Win XP (sp2) Reporter: Andrew Redhead Using an ejb-jar.xml file to inject an EntityManger into an EJB3 stateless session bean succeeds for bean interface methods but fails for @PostConstruct methods. In both cases the reference to the EntityManager is non-null, however in the @PostConstruct method, accessing the EnityManger underlying delegate fails. The test cases provide both an "API" interface case (which passes) and an @PostConstruct case, which currently fails. -- 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

17 years

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-1063) For task creation/modification, prepopulate form fields/buttons in 'Generate Task Form' from xhtml if file exists.

by Chris Whalen (JIRA)

For task creation/modification, prepopulate form fields/buttons in 'Generate Task Form' from xhtml if file exists. ------------------------------------------------------------------------------------------------------------------- Key: JBPM-1063 URL: http://jira.jboss.com/jira/browse/JBPM-1063 Project: JBoss jBPM Issue Type: Feature Request Reporter: Chris Whalen Assigned To: Tom Baeyens -- 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

17 years

3
3
0 / 0

[JBoss JIRA] Created: (GPD-74) Add a server adaptor to enable starting and stopping the 'jbpm server'.

by Koen Aers (JIRA)

Add a server adaptor to enable starting and stopping the 'jbpm server'. ----------------------------------------------------------------------- Key: GPD-74 URL: http://jira.jboss.com/jira/browse/GPD-74 Project: JBoss jBPM GPD Issue Type: Task Reporter: Koen Aers Assigned To: Koen Aers -- 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

17 years

1
4
0 / 0

[JBoss JIRA] Created: (GPD-37) include snap to grid

by Koen Aers (JIRA)

include snap to grid -------------------- Key: GPD-37 URL: http://jira.jboss.com/jira/browse/GPD-37 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers While designing processes, it would be a lot easier if there is some kind of 'snap to grid'. You can then have easier manual allignment etc. Besides that, the images look better - transitions should snap to the grid to - transitions should be perpendicular at least if there are more than three points in the line -- 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

17 years

3
3
0 / 0

[JBoss JIRA] Created: (JBJMX-99) Ant task <jmx><setAttribute> problem : unable to use <value> tag inside

by Benoit Lavenier (JIRA)

Ant task <jmx><setAttribute> problem : unable to use <value> tag inside ----------------------------------------------------------------------- Key: JBJMX-99 URL: http://jira.jboss.com/jira/browse/JBJMX-99 Project: JBoss JMX Issue Type: Bug Affects Versions: JBossAS-4.0.0 Environment: Windows XP, JRE 1.5 Eclipse 3.2 Ant 1.6.5 Reporter: Benoit Lavenier The Ant task JMX (org.jboss.ant.JMX) has a code error in the subclass "Setter" (used by <setAttribute> sub task) The methode named setValue in Setter subclass should be "addValue" Please refer to the folowwing url : http://ant.apache.org/manual/develop.html , and the "Supporting nested elements" section I think the following code will works fine : // "setValue" method (of subclass Setter) remaned in "addValue" public void addValue(Param value) { // This will only consider the last <value> tag, if more than one tag this.value = value; } -- 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

17 years

3
2
0 / 0

[JBoss JIRA] Created: (JGRP-549) ConnectionTable: spurious Connection instances on concurrent connects

by Bela Ban (JIRA)

ConnectionTable: spurious Connection instances on concurrent connects --------------------------------------------------------------------- Key: JGRP-549 URL: http://jira.jboss.com/jira/browse/JGRP-549 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 If we have members A and B, and they don't yet have connections to each other, and start sending messages to each other at the exact same time, then we run into the following scenario: - A attempts to connect to B (new Socket()) - B attempts to connect to A - A accepts B's connection and adds an entry for B into its table - B adds an entry for A into its table - B gets the accept() from A, but doesn't add the new Connection into its table because there is already a Connection. This leads to a spurious Connection object, which will only be closed and garbage collected once A or B leaves the cluster - We used to close Connections which were already in the table, but this lead to ping-pong effects where concurrent initial senders always closed each others connections - Even worse: a new Socket() always creates a new Connection object and places it into the table, *regardless* of whether a Connection for a given destination already exists or not ! GOAL: #1 Have only 1 TCP connection between any 2 members #2 Establish a handshaking mechanism, to avoid spurious connections SOLUTION: - When A establishes a connection to B, A needs to get agreement from B first (and vice versa) -- 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

17 years

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-4558) Connection Timeout Immediately After ACKing A Request

by Mike Millson (JIRA)

Connection Timeout Immediately After ACKing A Request ----------------------------------------------------- Key: JBAS-4558 URL: http://jira.jboss.com/jira/browse/JBAS-4558 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-4.0.2 Final Reporter: Mike Millson Assigned To: Thomas Diesler The customer has an application that periodically sends Web service requests to JBoss AS every 20 secs in sets of 4, to check wether the Web Service is up. They find that JBoss AS occasionally drops the request packets when the HTTP connector timeout is set to 20 seconds. When this happens, the packet sequence is very strange. Attached is an example packet sequence viewable using ethereal/WireShark. #275: Client sends request >20 seconds after #274 acknowledgment #276: Server sends ACK for #275 #277: Server sends connection timeout FIN/ACK #278 Client sends combined ACK for #277 and FIN/ACK #279 Server sends ACK for #278 Packet #275 was more than 20 seconds after the last packet was sent; however, it was received before the server initiated the connection timeout sequence in packets #277-279. It seems to be unaware of the ACK in #276. Almost as if the timeout sequence started, then before the FIN/ACK could be sent, another packet was received and acknowledged. Some sort of timing issue when a request is sent at the same time a connection times 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

17 years

3
4
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 September 2007