[JBoss JIRA] (AS7-6086) Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6086?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6086:
----------------------------------------------
Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 922340|https://bugzilla.redhat.com/show_bug.cgi?id=922340] from ON_QA to VERIFIED
> Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler
> ---------------------------------------------------------------------------------------
>
> Key: AS7-6086
> URL: https://issues.jboss.org/browse/AS7-6086
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Doesn't matter.
> Reporter: Krzysztof Noceń
> Assignee: Eduardo Martins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP)
>
>
> Class:
> {code}
> org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler
> {code}
> Method:
> {code}
> public void processMessage(ChannelAssociation, MessageInputStream) throws IOException;
> {code}
> This code fragment:
> {code}
> try {
> methodParams[i] = unmarshaller.readObject();
> } catch (ClassNotFoundException cnfe) {
> /.../
> return;
> }
> {code}
> doesn't catch *java.lang.IllegalArgumentException*.
> This causes the server hangs.
> Example stacktrace:
> {code}
> java.lang.IllegalArgumentException: No enum const org.example.ExampleEnum.ENUM_VALUE
> at java.lang.Enum.valueOf(Enum.java:196)
> at org.jboss.marshalling.river.RiverUnmarshaller.resolveEnumConstant(RiverUnmarshaller.java:1549)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1293)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:164)
> at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:182)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:429)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> {code}
> I caught *java.lang.Exception*. It helps.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6086) Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6086?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6086:
----------------------------------------------
Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 922340|https://bugzilla.redhat.com/show_bug.cgi?id=922340]
reproduced manually: OK
regression testing: OK
checked that the fixed code is present in the source jar: OK
md5sum of patch files:
e4d2dfecf160cfb828541b73de964e41 ./modules/org/jboss/as/ejb3/main/jboss-as-ejb3-7.1.3.Final-redhat-4-bz-922340.jar
74fdb27b0f93564054f35c02bd063f77 ./modules/org/jboss/as/ejb3/main/module.xml
md5sum of additional source jar:
aa6cd8acb6628ba64f7a8697a3499faf jboss-as-ejb3-7.1.3.Final-redhat-4-sources-bz-922340.jar
> Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler
> ---------------------------------------------------------------------------------------
>
> Key: AS7-6086
> URL: https://issues.jboss.org/browse/AS7-6086
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Doesn't matter.
> Reporter: Krzysztof Noceń
> Assignee: Eduardo Martins
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP)
>
>
> Class:
> {code}
> org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler
> {code}
> Method:
> {code}
> public void processMessage(ChannelAssociation, MessageInputStream) throws IOException;
> {code}
> This code fragment:
> {code}
> try {
> methodParams[i] = unmarshaller.readObject();
> } catch (ClassNotFoundException cnfe) {
> /.../
> return;
> }
> {code}
> doesn't catch *java.lang.IllegalArgumentException*.
> This causes the server hangs.
> Example stacktrace:
> {code}
> java.lang.IllegalArgumentException: No enum const org.example.ExampleEnum.ENUM_VALUE
> at java.lang.Enum.valueOf(Enum.java:196)
> at org.jboss.marshalling.river.RiverUnmarshaller.resolveEnumConstant(RiverUnmarshaller.java:1549)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1293)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:164)
> at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:182)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:429)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> {code}
> I caught *java.lang.Exception*. It helps.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6367) Allow more flexibility in the way EJB authentication is handled with regards to remoting and security-realms
by Alexey Tomin (JIRA)
[ https://issues.jboss.org/browse/AS7-6367?page=com.atlassian.jira.plugin.s... ]
Alexey Tomin commented on AS7-6367:
-----------------------------------
Sorry, for work JMS client with custom roles module need sets:
Hashtable<String, Object> params = new Hashtable<String, Object>();
...........
params.put("jboss.naming.client.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT", "false"); <-- for allow plain mechanism
params.put(Context.SECURITY_PRINCIPAL, JMS_LOGIN); <-- for org.jboss.security.auth.spi.UsernamePasswordLoginModule
params.put(Context.SECURITY_CREDENTIALS, JMS_PASSWORD); <-- org.jboss.security.auth.spi.UsernamePasswordLoginModule
Context context = new InitialContext(params);
> Allow more flexibility in the way EJB authentication is handled with regards to remoting and security-realms
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6367
> URL: https://issues.jboss.org/browse/AS7-6367
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Derek Horton
> Assignee: jaikiran pai
>
> My confusion is around the remoting/security-realm setup in the use case
> where multiple EJBs are deployed that use different security-domains and
> the EJBs will be invoked by remote standalone clients. For example,
> ejbX needs to be in the sec-domain-X security-domain, while ejbY needs to
> be in the sec-domain-Y security-domain.
> In this situation, the authentication checks are going to be handled by
> the security-realm that is associated with the remote connector that is
> configured to be used by the EJB subsystem.
> It looks like the security-realm can either handle the authentication
> checks directly (properties file, ldap, etc) or it can defer to the
> jaas security-domain. In both of those situations, it seems that the
> EJBs are limited to a single authentication point. The EJB
> authentication is either going to be handled by a single security-realm
> or the security-realm will defer to a single security-domain.
> I could configure the security-domain to have multiple login modules. I
> assume the same thing could be done with the security-realm.
> Basically the problem that I am trying to solve boils down to this: the
> authentication checks for remote EJBs appear to be checked by either a
> single security-realm or a single security-domain. Is there a way to
> change this?
> One idea I had was to add another remote connector to the EJB subsystem.
> Unfortunately, this does not appear to be possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6803) NicInterfaceCriteriaUnitTestCase testBasic fails on a host configured with a dual IP stack
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-6803?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek commented on AS7-6803:
-------------------------------------
@Ondra
Why did you assigne this JIRA to me? I'm not involved in AS8 development, nor author of these testcases.
> NicInterfaceCriteriaUnitTestCase testBasic fails on a host configured with a dual IP stack
> ------------------------------------------------------------------------------------------
>
> Key: AS7-6803
> URL: https://issues.jboss.org/browse/AS7-6803
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.0.0.Alpha1
> Reporter: Michael Musgrove
> Assignee: Pavel Janousek
>
> This test fails when we run the test suite with the following IPv6 options:
> {noformat}
> -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.bind.address=[::1] -Djboss.bind.address.management=[::1] -Djboss.bind.address.unsecure=[::1]
> {noformat}
>
> It appears that the test is expecting an array containing one nic address but instead gets two (IPv4 and IPv6) addresses. The linked JBTM jira is where we initially reported the issue. Test output is:
> {noformat}
> Failed tests:
> testBasic(org.jboss.as.controller.interfaces.NicInterfaceCriteriaUnitTestCase): expected:<[/0:0:0:0:0:0:0:1%1]> but was:<[/0:0:0:0:0:0:0:1%1, /127.0.0.1]>
> testMultipleCriteria(org.jboss.as.controller.interfaces.NotInterfaceCriteriaUnitTestCase): expected:<{name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2]}> but was:<{name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2, /172.17.131.3]}>
> testMultipleCriteria(org.jboss.as.controller.interfaces.AnyInterfaceCriteriaUnitTestCase): expected:<{name:lo (lo)=[/0:0:0:0:0:0:0:1%1], name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2]}> but was:<{name:lo (lo)=[/127.0.0.1, /0:0:0:0:0:0:0:1%1], name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2, /172.17.131.3]}>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6803) NicInterfaceCriteriaUnitTestCase testBasic fails on a host configured with a dual IP stack
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-6803?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek reassigned AS7-6803:
-----------------------------------
Assignee: Ondrej Zizka (was: Pavel Janousek)
> NicInterfaceCriteriaUnitTestCase testBasic fails on a host configured with a dual IP stack
> ------------------------------------------------------------------------------------------
>
> Key: AS7-6803
> URL: https://issues.jboss.org/browse/AS7-6803
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.0.0.Alpha1
> Reporter: Michael Musgrove
> Assignee: Ondrej Zizka
>
> This test fails when we run the test suite with the following IPv6 options:
> {noformat}
> -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.bind.address=[::1] -Djboss.bind.address.management=[::1] -Djboss.bind.address.unsecure=[::1]
> {noformat}
>
> It appears that the test is expecting an array containing one nic address but instead gets two (IPv4 and IPv6) addresses. The linked JBTM jira is where we initially reported the issue. Test output is:
> {noformat}
> Failed tests:
> testBasic(org.jboss.as.controller.interfaces.NicInterfaceCriteriaUnitTestCase): expected:<[/0:0:0:0:0:0:0:1%1]> but was:<[/0:0:0:0:0:0:0:1%1, /127.0.0.1]>
> testMultipleCriteria(org.jboss.as.controller.interfaces.NotInterfaceCriteriaUnitTestCase): expected:<{name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2]}> but was:<{name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2, /172.17.131.3]}>
> testMultipleCriteria(org.jboss.as.controller.interfaces.AnyInterfaceCriteriaUnitTestCase): expected:<{name:lo (lo)=[/0:0:0:0:0:0:0:1%1], name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2]}> but was:<{name:lo (lo)=[/127.0.0.1, /0:0:0:0:0:0:0:1%1], name:eth0 (eth0)=[/fe80:0:0:0:216:3eff:fe0e:a61c%2, /172.17.131.3]}>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6699) AS7 messaging resources throws NPE when hornetq-server is a backup
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6699?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6699:
----------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 918131|https://bugzilla.redhat.com/show_bug.cgi?id=918131] from POST to MODIFIED
> AS7 messaging resources throws NPE when hornetq-server is a backup
> ------------------------------------------------------------------
>
> Key: AS7-6699
> URL: https://issues.jboss.org/browse/AS7-6699
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 8.0.0.Alpha1
>
>
> steps to reproduce:
> Configure AS7's hornetq-server to be a backup ready for failover.
> Run AS7 standalone-full configuration with hornetq-server configured to be a backup:
> {noformat}
> <hornetq-server>
> <backup>true</backup>
> ...
> {noformat}
> The AS7 will start, its hornetq-server too *but* it will not be active:
> {noformat}
> 18:24:56,527 INFO [org.hornetq.core.server] (HQ119001: Activation for server HornetQServerImpl::serverUUID=349065dd-87f2-11e2-911d-f19bf97ea7a7) HQ002211: HornetQ Backup Server version 2.3.0.CR1 (buzzzzz!, 122) [349065dd-87f2-11e2-911d-f19bf97ea7a7] started, waiting live to fail before it gets active
> {noformat}
> The hornetq server will not become active until a live node fails. When this occurs, the server will become active, accept connection, create core and JMS resources etc.
> The issue is that any runtime operation on a hornetq-server's children will fail.
> The runtime operations rely on HornetQ's management resource (eg TopicControl, QueueControl) and these objects are not available until HornetQ server is active.
> For AS7 integration that means that we must somehow prevent any runtime changes to any hornetq-server's children resources for a passive server. There are no corresponding runtime resources in HornetQ for them.
> Additionnaly, hornetq-server does not expose the "active" runtime attribute to know whether the server is active.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6711) Unable to restart server group in domain mode
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6711?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6711:
----------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 913236|https://bugzilla.redhat.com/show_bug.cgi?id=913236] from POST to MODIFIED
> Unable to restart server group in domain mode
> ---------------------------------------------
>
> Key: AS7-6711
> URL: https://issues.jboss.org/browse/AS7-6711
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Brian Stansberry
> Assignee: Emanuel Muckenhuber
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
> Attachments: AS7-6711-threads.txt
>
>
> Restarting the servers in the standard domain.xml main-server-group will result in a hang in the CLI and in the master HC.
> To reproduce start the standard domain.sh and in another window launch the CLI and:
> [domain@localhost:9999 /] /server-group=main-server-group:restart-servers
> Resulting console log output:
> [Host Controller] 18:17:30,511 INFO [org.jboss.as.host.controller] (management-handler-thread - 3) JBAS010923: Stopping server server-one
> 18:17:30,515 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012018: Stopping process 'Server:server-one'
> [Server:server-one] 18:17:30,599 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
> [Server:server-one] 18:17:30,600 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
> [Server:server-one] 18:17:30,611 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003075: Coyote HTTP/1.1 pausing on: http-localhost/127.0.0.1:8080
> [Server:server-one] 18:17:30,612 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003077: Coyote HTTP/1.1 stopping on : http-localhost/127.0.0.1:8080
> [Server:server-one] 18:17:30,616 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 79) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> [Server:server-one] 18:17:30,615 INFO [org.apache.catalina.core] (MSC service thread 1-2) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
> [Server:server-one] 18:17:30,640 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = h2
> [Server:server-one] 18:17:30,664 INFO [org.hornetq.ra] (MSC service thread 1-4) HQ151005: HornetQ resource adaptor stopped
> [Server:server-one] 18:17:30,704 INFO [org.hornetq.core.server] (MSC service thread 1-3) HQ221004: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [93f152f7-8aa1-11e2-8c0e-99b598ec3b97] stopped
> [Host Controller] 18:17:30,722 INFO [org.jboss.as.host.controller] (Remoting "pingguo.local:MANAGEMENT" read-1) JBAS010926: Unregistering server server-one
> [Server:server-one] 18:17:30,754 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015950: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" stopped in 189ms
> [Server:server-one]
> 18:17:30,815 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) JBAS012010: Process 'Server:server-one' finished with an exit status of 0
> [Host Controller] 18:17:30,818 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering server server-one
> [Host Controller] 18:17:30,836 INFO [org.jboss.as.host.controller] (management-handler-thread - 3) JBAS010922: Starting server server-one
> 18:17:30,845 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012017: Starting process 'Server:server-one'
> [Server:server-one] 18:17:31,676 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR2
> [Server:server-one] 18:17:32,178 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.1.Final
> [Server:server-one] 18:17:32,332 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
> [Server:server-one] 18:17:32,530 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.1.0.Beta9
> [Server:server-one] 18:17:32,538 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.1.0.Beta9
> [Server:server-one] 18:17:32,559 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.15.GA
> [Host Controller] 18:17:33,607 INFO [org.jboss.as.domain.controller.mgmt] (Remoting "pingguo.local:MANAGEMENT" task-16) JBAS010920: Server [Server:server-one] registered using connection [Channel ID 2bacdeb7 (inbound) of Remoting connection 49660c5f to /127.0.0.1:60647]
> After that everything hangs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6683) Fail to start the messaging subsystem when a connector is not defined
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6683?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6683:
----------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 915369|https://bugzilla.redhat.com/show_bug.cgi?id=915369] from POST to MODIFIED
> Fail to start the messaging subsystem when a connector is not defined
> ---------------------------------------------------------------------
>
> Key: AS7-6683
> URL: https://issues.jboss.org/browse/AS7-6683
> Project: Application Server 7
> Issue Type: Feature Request
> Components: JMS
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Jeff Mesnil
> Assignee: Bartosz Baranowski
> Fix For: 8.0.0.Alpha1
>
> Attachments: AS7-6683.patch
>
>
> <connectors>
> <netty-connector name="netty" socket-binding="messaging"/>
> <netty-connector name="netty-throughput" socket-binding="messaging-throughput">
> <param key="batch-delay" value="50"/>
> </netty-connector>
> <!--
> <netty-connector name="connector-to-proxy-directing-to-this-server" socket-binding="binding-connect-to-this-server-through-remote-proxy"/>
> -->
> <in-vm-connector name="in-vm" server-id="0"/>
> </connectors>
> <broadcast-groups>
> <broadcast-group name="bg-group1">
> <socket-binding>messaging-group</socket-binding>
> <broadcast-period>2000</broadcast-period>
> <connector-ref>
> connector-to-proxy-directing-to-this-server
> </connector-ref>
> </broadcast-group>
> </broadcast-groups>
> Additional info:
> 15:56:47,200 WARN [org.hornetq.core.server] (MSC service thread 1-5) HQ222185: There is no connector deployed with name {0}. The broadcast group with name {1} will not be deployed.
> 15:56:47,201 ERROR [org.hornetq.core.server] (MSC service thread 1-5) HQ224002: Failure in initialisation: java.lang.NullPointerException
> at org.hornetq.core.server.management.impl.ManagementServiceImpl.registerBroadcastGroup(ManagementServiceImpl.java:346) [hornetq-server-2.3.0.CR1.jar:]
> at org.hornetq.core.server.cluster.ClusterManager.deployBroadcastGroup(ClusterManager.java:815) [hornetq-server-2.3.0.CR1.jar:]
> at org.hornetq.core.server.cluster.ClusterManager.deploy(ClusterManager.java:225) [hornetq-server-2.3.0.CR1.jar:]
> at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart1(HornetQServerImpl.java:1414) [hornetq-server-2.3.0.CR1.jar:]
> at org.hornetq.core.server.impl.HornetQServerImpl.access$1000(HornetQServerImpl.java:164) [hornetq-server-2.3.0.CR1.jar:]
> at org.hornetq.core.server.impl.HornetQServerImpl$SharedNothingLiveActivation.run(HornetQServerImpl.java:2496) [hornetq-server-2.3.0.CR1.jar:]
> at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:416) [hornetq-server-2.3.0.CR1.jar:]
> at org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:464) [hornetq-jms-server-2.3.0.CR1.jar:]
> at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:74) [jboss-as-messaging-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38]
> 15:56:47,205 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.messaging.default.jms.manager: org.jboss.msc.service.StartException in service jboss.messaging.default.jms.manager: java.lang.NullPointerException
> at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:97)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38]
> Caused by: java.lang.NullPointerException
> at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:78)
> ... 5 more
> HornetQ logs a WARN when a referenced connector is not defined. AS7 should be more careful and reject the operation if that the case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBMESSAGING-1943) HeuristicMixedException gets thrown if the destination has reached its maxsize
by Tyronne Wickramarathne (JIRA)
Tyronne Wickramarathne created JBMESSAGING-1943:
---------------------------------------------------
Summary: HeuristicMixedException gets thrown if the destination has reached its maxsize
Key: JBMESSAGING-1943
URL: https://issues.jboss.org/browse/JBMESSAGING-1943
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.8.SP5
Environment: JBoss-EAP-5.1.2, JBossMessaging-1.4.8-SP5, JBossTS-4.6.1GA-CP11 +JBTM-842 &J BTM-924
Reporter: Tyronne Wickramarathne
Assignee: Yong Hao Gao
The message producer throws a HeuristicMixedException when trying to send messages to a destination which has reached its maxsize.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month