[JBoss JIRA] Created: (JBMESSAGING-1832) Client.removeListener() should be called before Client.disconnect() is called.
by Yong Hao Gao (JIRA)
Client.removeListener() should be called before Client.disconnect() is called.
------------------------------------------------------------------------------
Key: JBMESSAGING-1832
URL: https://jira.jboss.org/browse/JBMESSAGING-1832
Project: JBoss Messaging
Issue Type: Bug
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
(From Ron)
there are a bunch of Remoting threads that are created but not
> destroyed. These are BisocketServerInvoker$ControlConnectionThreads.
> They run on the client and handle "create connection" requests from
> the server coming in on the control connection.
>
> When org.jboss.remoting.Client.addListener() is called, a
> BisocketServerInvoker is created on the client side, and a
> BisocketServerInvoker$ControlConnectionThread is created. When
> Client.removeListener() is called, the
> BisocketServerInvoker$ControlConnectionThread is shut down. But in
> this case (and it happened in one other support case), the number of
> BisocketServerInvoker$ControlConnectionThreads just keeps growing. I
> created a jboss-remoting.jar with extra logging which shows that
> JBossMessaging doesn't seem to be calling Client.removeListener()
> before it calls Client.disconnect().
>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (JBRULES-2818) Deploy Task Service as Jboss Service
by Cristiano Nicolai (JIRA)
Deploy Task Service as Jboss Service
------------------------------------
Key: JBRULES-2818
URL: https://jira.jboss.org/browse/JBRULES-2818
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-process-task
Affects Versions: 5.1.1.FINAL
Environment: Jboss AS 5.1
Reporter: Cristiano Nicolai
Assignee: Mark Proctor
Deploy a new Jboss Service (.sar) with the required jars to start the MinaTaskServer and manage it using admin-console.
The drools-process-task jar shouldn't package the persistence.xml file because will cause the server to try to deploy the persistence unit.
In order to have the mbean exposed in the admin-console I included the following in the rhq-plugin.xml:
<service name="Drools Task Server"
description="Drools Task Server"
displayName="Drools Task Server"
discovery="org.rhq.plugins.jmx.MBeanResourceDiscoveryComponent"
class="org.rhq.plugins.jmx.MBeanResourceComponent">
<runs-inside>
<parent-resource-type name="JMX Server" plugin="JMX"/>
<parent-resource-type name="JBossAS Server" plugin="JBossAS"/>
<parent-resource-type name="JBossAS Server" plugin="JBossAS5"/>
</runs-inside>
<plugin-configuration>
<c:simple-property name="objectName" readOnly="true" default="org.drools:type=DroolsTaskServer"/>
</plugin-configuration>
<operation name="start" displayName="Start" />
<operation name="stop" displayName="Stop" />
</service>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (JBAS-5745) ServerMBean.InShutdown flag won't turn on when the shutdown hook is called directly
by Takayoshi Kimura (JIRA)
ServerMBean.InShutdown flag won't turn on when the shutdown hook is called directly
-----------------------------------------------------------------------------------
Key: JBAS-5745
URL: http://jira.jboss.com/jira/browse/JBAS-5745
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: System service
Affects Versions: JBossAS-5.0.0.CR1, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA, JBossAS-4.0.4.GA
Reporter: Takayoshi Kimura
Assigned To: Dimitris Andreadis
The ServerMBean.InShutdown flag is only turned on when the shutdown() operation is called. There is another shutdown path, a shutdown hook called by signals including Ctrl+c. This flag is needed to update in the shutdownHook.shutdown() method to reflect the sever status.
--
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
13 years, 6 months
[JBoss JIRA] Created: (JBBUILD-656) RichFaces project: current build problems
by Ilya Shaikovsky (JIRA)
RichFaces project: current build problems
-----------------------------------------
Key: JBBUILD-656
URL: https://jira.jboss.org/browse/JBBUILD-656
Project: JBoss Build System
Issue Type: Bug
Components: Artifact Repositories
Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 22:16:01+0300)
Java version: 1.6.0_20
Reporter: Ilya Shaikovsky
1) https://jira.jboss.org/browse/RF-9483 - I was not able to build RF 3.3.3 as far as moved my environment to new PC (except local maven repo :( )
Note - removing wagon dependency I'm running with another "not found" issues. Last time when I succesfully tried with clean repo and it was fine - was before going to Nexus.
2) I even can't build the RF-4.0.0 project with *clean install* getting
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.maven.plugins:maven-clean-plugin
Reason: POM 'org.apache.maven.plugins:maven-clean-plugin' not found in repositor
y: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-clean-plugin:pom:2.3
from the specified remote repositories:
jboss-deprecated (https://repository.jboss.org/nexus/content/repositories/depr
ecated/),
jboss-public-repository-group (http://repository.jboss.org/nexus/content/group
s/public/)
Note - works if execute just install for sure.. all the other dependencies fine.
Check my environment and my settings.xml attached. Sorry if missed something obvious during migration and please point me to the right direction in that case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months