[JBoss JIRA] Created: (JGRP-1090) Many retransmissions with message bundling and OOB messages
by Bela Ban (JIRA)
Many retransmissions with message bundling and OOB messages
-----------------------------------------------------------
Key: JGRP-1090
URL: https://jira.jboss.org/jira/browse/JGRP-1090
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.9
When message bundling is enabled, we queue *regular* messages until max_bundle_size has been reached or max_bundle_timeout has exceeded.
The problem is that - when sending OOB (as opposed to regular) messages - they're *not* queued. This means the OOB message is possibly received *before* the regular messages and thus causes retransmission !
E.g. we send regular message 1-10, then OOB message 11.
Say 1-3 are sent immediately (because the bundle timeout kicked in or the size was exceeded). Messages 4-10 are queued and sent later. Message 11 is sent immediately.
On the receiver side, message reception could be for example: 1-3, 11, 4-10
When OOB message 11 is received, the receiver asks for retransmission of messages 4-10 !
This is not incorrect, but causes a lot of unneeded retransmissions !
public static void main(String[] args) throws Exception {
JChannel c1=new JChannel("/home/bela/fast.xml");
c1.connect("bla3");
JChannel c2=new JChannel("/home/bela/fast.xml");
c2.connect("bla3");
for(int i=1; i <= 20; i++) {
c1.send(null, null, "hello-" + i);
}
Message oob_msg=new Message(null, null, "oob msg");
oob_msg.setFlag(Message.OOB);
c1.send(oob_msg);
Util.sleep(20000);
Util.close(c2, c1);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Created: (JBAS-7905) Fix the WARN messages logged during AS shutdown
by jaikiran pai (JIRA)
Fix the WARN messages logged during AS shutdown
-----------------------------------------------
Key: JBAS-7905
URL: https://jira.jboss.org/jira/browse/JBAS-7905
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Environment: AS trunk
Reporter: jaikiran pai
Fix For: JBossAS-6.0.0.M3
JBoss AS on shutdown (or even undeploy of applications) logs these WARN messages:
16:26:16,671 WARN [ClassLoading] Exception unregistering module, registry: org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback@1762fc7,
cause: java.lang.IllegalStateException: Module VFSDeploymentClassLoaderPolicyModule juddi-service.sar:0.0.0 is not registered
16:26:16,672 WARN [ClassLoading] Exception unregistering module, registry: org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback@1762fc7, cause: java.lang.IllegalStateException: Module VFSDeploymentClassLoaderPolicyModule jsr88-service.xml:0.0.0 is not registered
16:26:16,673 WARN [ClassLoading] Exception unregistering module, registry: org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback@1762fc7,cause: java.lang.IllegalStateException: Module
VFSDeploymentClassLoaderPolicyModule jgroups-channelfactory.sar:0.0.0 is not registered
Either these should be logged at a lower level or the root cause needs to be fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Created: (JBREFLECT-116) Errors on shutdown in JBossClDelegatingClassPoolRepository.unregisterClassLoader()
by Kabir Khan (JIRA)
Errors on shutdown in JBossClDelegatingClassPoolRepository.unregisterClassLoader()
----------------------------------------------------------------------------------
Key: JBREFLECT-116
URL: https://jira.jboss.org/jira/browse/JBREFLECT-116
Project: JBoss Reflection
Issue Type: Feature Request
Affects Versions: JBossReflection.2.2.0-Alpha4
Reporter: Kabir Khan
Assignee: Kabir Khan
Fix For: JBossReflection.2.2.0-Alpha5
Getting errors on shutdown/undeployment in AS due to JBossClDelegatingClassPoolRepository.registerClassLoader() not registering the modules so there is no pool in registeredModules when we undeploy and call JBossClDelegatingClassPoolRepository.unregisterClassLoader().
--------------------------------------------
Kabir: So, it seems that registerClassLoader() only gets called if someone attempts to use the pool? Flavia, how is this supposed to work?
Ales: I thought there would be symmetric invocations,
but I'll let Flavia explain more.
Kabir: In any case, as a temporary measure (I can't remember if Flavia is on holidays this week) I think it should be fine not to throw the exception from unregisterClassLoader()
Ales: Yup, she's on vacation -- home moving stuff.
Can you change this -- and we'll deal with any issues later?
Is this in Classpools or AOP?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Created: (JBAOP-787) Scoping of MC beans is broken
by Carlo de Wolf (JIRA)
Scoping of MC beans is broken
-----------------------------
Key: JBAOP-787
URL: https://jira.jboss.org/jira/browse/JBAOP-787
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Carlo de Wolf
Installing the following test-aop.xml:
<?xml version="1.0" encoding="UTF-8"?>
<aop xmlns="urn:jboss:aop-beans:1.0">
<domain name="Test Aspect Domain 1">
<stack name="Test Stack"/>
</domain>
<domain name="Test Aspect Domain 2">
<stack name="Test Stack"/>
</domain>
</aop>
gives:
15:30:21,925 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to PostClassLoader: name=vfs:///home/carlo/work/jboss-head/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/test-aop.xml state=ClassLoader mode=Manual requiredState=PostClassLoader: org.jboss.deployers.spi.DeploymentException: org.jboss.deployers.spi.DeploymentException: Error deploying: Test Stack
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer.deployBeans(AbstractAopMetaDataDeployer.java:296) [:2.2.0.Final]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer.deploy(AbstractAopMetaDataDeployer.java:133) [:2.2.0.Final]
at org.jboss.aop.asintegration.jboss5.AOPDeploymentAopMetaDataDeployer.deploy(AOPDeploymentAopMetaDataDeployer.java:46) [:2.2.0.Final]
at org.jboss.aop.asintegration.jboss5.AOPDeploymentAopMetaDataDeployer.deploy(AOPDeploymentAopMetaDataDeployer.java:36) [:2.2.0.Final]
at org.jboss.deployers.vfs.spi.deployer.AbstractSimpleVFSRealDeployer.deploy(AbstractSimpleVFSRealDeployer.java:56) [:2.2.0.Alpha4]
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.Alpha4]
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1857) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1575) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1516) [:2.2.0.Alpha4]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2042) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1081) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1320) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1244) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1137) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:937) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:652) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:2008) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1101) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha4]
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) [:6.0.0-SNAPSHOT]
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409) [:6.0.0-SNAPSHOT]
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294) [:6.0.0-SNAPSHOT]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_15]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_15]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_15]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_15]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_15]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_15]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_15]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_15]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_15]
Caused by: org.jboss.deployers.spi.DeploymentException: Error deploying: Test Stack
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.Alpha4]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer$MyBeanMetaDataDeployer.deploy(AbstractAopMetaDataDeployer.java:367) [:2.2.0.Final]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer$MyBeanMetaDataDeployer.access$100(AbstractAopMetaDataDeployer.java:329) [:2.2.0.Final]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer.deployBeans(AbstractAopMetaDataDeployer.java:269) [:2.2.0.Final]
... 33 more
Caused by: java.lang.IllegalStateException: Test Stack is already installed.
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:833) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:639) [jboss-dependency.jar:2.2.0.Alpha9]
at org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer$MyBeanMetaDataDeployer.deploy(AbstractAopMetaDataDeployer.java:363) [:2.2.0.Final]
... 35 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Created: (JBAS-4344) Problematic casting to String in org.jboss.jmx.connector.invoker.AuthenticationInterceptor
by David Dossot (JIRA)
Problematic casting to String in org.jboss.jmx.connector.invoker.AuthenticationInterceptor
------------------------------------------------------------------------------------------
Key: JBAS-4344
URL: http://jira.jboss.com/jira/browse/JBAS-4344
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: JBossAS-4.0.4.GA
Environment: Mac Os X, RedHat
Reporter: David Dossot
Assigned To: Dimitris Andreadis
There is a problematic cast in org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(Invocation invocation) on line 110:
String opname = (String) obj[1];
When Twiddling to get a particular attribute, the following code is used in org.jboss.console.twiddle.command.GetCommand.execute(String[] args) on line 165:
attributeNames.toArray(names);
(...)
AttributeList attrList = server.getAttributes(objectName, names);
So obj[1] ends up holding a String[] of attribute names (even if there is only one) and the cast fails:
14:14:44,760 ERROR [Twiddle] Exec failed
java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String
at org.jboss.jmx.connector.invoker.AuthorizationInterceptor.invoke(AuthorizationInterceptor.java:107)
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
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:589)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
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:589)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:679)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:704)
at java.lang.Thread.run(Thread.java:637)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:331)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:194)
at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy0.getAttributes(Unknown Source)
at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:168)
at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305)
--
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, 3 months