[JBoss JIRA] Created: (JBAS-3548) RMIAdaptorUnitTestCase testMBeanInfoMarshalling failures
by Matt Wringe (JIRA)
RMIAdaptorUnitTestCase testMBeanInfoMarshalling failures
--------------------------------------------------------
Key: JBAS-3548
URL: http://jira.jboss.com/jira/browse/JBAS-3548
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.5.0_08 JVM
RHEL 4, Linux Kernel 2.6.9
Reporter: Matt Wringe
The org.jboss.test.jmx.test.RMIAdaptorUnitTestCase testMBeanInfoMarshalling test fails on the Sun 1.5.0 JVM.
>From the test report:
"Failed to get MBeanInfo for bean named: jboss.deployment:type=DeploymentScanner,flavor=URL
junit.framework.AssertionFailedError: Failed to get MBeanInfo for bean named: jboss.deployment:type=DeploymentScanner,flavor=URL
at org.jboss.test.jmx.test.RMIAdaptorUnitTestCase.testMBeanInfoMarshalling(RMIAdaptorUnitTestCase.java:72)"
--
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, 4 months
[JBoss JIRA] Created: (JBPM-742) Reimplement JbpmThreadsServlet as a ServletContextListener
by Alejandro Guizar (JIRA)
Reimplement JbpmThreadsServlet as a ServletContextListener
----------------------------------------------------------
Key: JBPM-742
URL: http://jira.jboss.com/jira/browse/JBPM-742
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM 3.1.1
Reporter: Alejandro Guizar
ServletContextListeners are a viable alternative to servlets for management of the jBPM scheduler/command threads. From the Servlet 2.4 spec, section 10.2:
>>>
Servlet event listeners support event notifications for state changes in the ServletContext, HttpSession and ServletRequest objects.
Servlet context listeners are used to **manage resources** or state held at a JVM level for the application.
<<<
Their intent definitely seems to match our purposes.
Further below:
>>>
There may be multiple listener classes listening to each event type.
<<<
We could have separate listeners for the scheduler and command executor so that applications may remove either of them in case the related service is not used.
Section 10.2.2 provides an example. When the application starts up, the listener creates a connection to the database and stores it in the servlet context. Servlets access the connection from the context as needed. When the application shuts down, the listener closes the connection.
Our listener could start the thread and store it in the servlet context, then stop it using the mechanisms provided by JBPM-741.
--
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, 4 months
[JBoss JIRA] Created: (JBPM-714) packaging just the webapp takes way to long
by Ronald van Kuijk (JIRA)
packaging just the webapp takes way to long
-------------------------------------------
Key: JBPM-714
URL: http://jira.jboss.com/jira/browse/JBPM-714
Project: JBoss jBPM
Issue Type: Feature Request
Affects Versions: jBPM 3.2 alpha 1
Environment: Eclipse 3.2, gpd 3.0.11, jdk 1.5 windhoos
Reporter: Ronald van Kuijk
Assigned To: Tom Baeyens
Fix For: jBPM 3.2
Packaging just the webapp takes 13 seconds. In this time the 'global' compile is used. This results in packaging jbpm-jpdl.jar twice and copying it to the repository twice.
This should be optimised in combination with a 'deploy' target which deploys it to a configured location.
Even better would be if it is a real WTP web (sub?) project which can have things like 'auto deployment' small updates to .xhtml files available immediately, 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, 4 months
[JBoss JIRA] Created: (JBMESSAGING-437) Non durable subscription optimization
by Tim Fox (JIRA)
Non durable subscription optimization
-------------------------------------
Key: JBMESSAGING-437
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-437
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.0.1.CR3
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.0.2
Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs.
Basically I think we can acknowledge them before they are sent from server to client.
This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks.
On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver.
This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time.
--
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, 4 months