[JBoss JIRA] Created: (JBJCA-531) NullPointerException at org.jboss.jca.core.workmanager.WorkManagerImpl.checkWorkCompletionException(WorkManagerImpl.java:635)
by Carlo de Wolf (JIRA)
NullPointerException at org.jboss.jca.core.workmanager.WorkManagerImpl.checkWorkCompletionException(WorkManagerImpl.java:635)
-----------------------------------------------------------------------------------------------------------------------------
Key: JBJCA-531
URL: https://issues.jboss.org/browse/JBJCA-531
Project: IronJacamar
Issue Type: Bug
Affects Versions: 1.0.0.Beta4
Reporter: Carlo de Wolf
Assignee: Jesper Pedersen
Priority: Critical
Given the code in WorkManagerImpl, wrapper might be null.
{noformat}
java.lang.NullPointerException
at org.jboss.jca.core.workmanager.WorkManagerImpl.checkWorkCompletionException(WorkManagerImpl.java:635)
at org.jboss.jca.core.workmanager.WorkManagerImpl.doWork(WorkManagerImpl.java:315)
at org.jboss.jca.core.workmanager.WorkManagerImpl.doWork(WorkManagerImpl.java:228)
at org.jboss.as.demos.ejb3.rar.SimpleQueueResourceAdapter.deliver(SimpleQueueResourceAdapter.java:70)
at org.jboss.as.demos.ejb3.mdb.PencasterMailCentre.specialDelivery(PencasterMailCentre.java:37)
... 63 more
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JGRP-1306) Custom thread factories, pools and timer overridden in Protocol.init()
by Paul Ferraro (JIRA)
Custom thread factories, pools and timer overridden in Protocol.init()
----------------------------------------------------------------------
Key: JGRP-1306
URL: https://issues.jboss.org/browse/JGRP-1306
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12
Reporter: Paul Ferraro
Assignee: Bela Ban
Priority: Minor
To override thread pools/factories/timer of a protocol, one must do the following:
UDP udp = new UDP();
udp.init(); // Creates default pools
udp.setThreadPool(...); // Destroys default pool first
If I try to avoid the unnecessary thread creation/destruction by the following:
UDP udp = new UDP();
udp.setThreadPool(...);
udp.init();
... then my custom pools get overridden by the default implementations.
Instead, Protocol.init() should check to see if implementations already exist before instantiating the default implementations.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBAS-9054) cli: execution of 'connect' while connected
by Alexey Loubyansky (JIRA)
cli: execution of 'connect' while connected
-------------------------------------------
Key: JBAS-9054
URL: https://issues.jboss.org/browse/JBAS-9054
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: 7.0.0.Beta2
Currently, 'connect' can be executed multiple times w/o any warnings that the connection has already been established.
For now I'll close the previously established connection, reconnect and log a message about what has happened.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBAS-9056) cli: reflect the connection status in the prompt
by Alexey Loubyansky (JIRA)
cli: reflect the connection status in the prompt
------------------------------------------------
Key: JBAS-9056
URL: https://issues.jboss.org/browse/JBAS-9056
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: 7.0.0.Beta2
There is no way currently to see whether the connection to the controller client has been established or not (you could try operation tab completion which works only when connected but that's not a very user friendly way).
The idea is to add the info right into the command line prompt.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months