[Design of Messaging on JBoss (Messaging/JBoss)] - Re: intermittent failures i am seeing
by clebert.suconic＠jboss.com
I kept calling "ant -Dtest-mask=ClientSessionStopStartTest integration-tests" until it failed... (about 4 times):
| [echo]
| [junit] Running org.jboss.messaging.tests.integration.client.ClientSessionStopStartTest
| [junit] main 08:20:24,939 INFO [UnitTestCase] ###### starting test testStopStartConsumerSyncReceiveImmediate
| [junit] main 08:20:25,019 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] main 08:20:25,284 INFO [UnitTestCase] ###### starting test testStopStartConsumerSyncReceive
| [junit] main 08:20:25,285 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] main 08:20:26,316 INFO [UnitTestCase] ###### starting test testStopStartConsumerAsyncSyncStoppedByHandler
| [junit] main 08:20:26,317 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] main 08:20:26,463 INFO [UnitTestCase] ###### starting test testStopStartConsumerAsyncSync
| [junit] main 08:20:26,464 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] Thread-3 (group:jbm-pinger-threads-169081233) 08:20:36,467 WARN [RemotingConnectionImpl] Connection failure has been detected Did not receive pong from server, active true client true:2
| [junit] main 08:20:36,480 WARN [ClientConsumerImpl] Timed out waiting for handler to complete processing
| [junit] main 08:20:36,485 INFO [UnitTestCase] ###### starting test testStopStartConsumerAsyncASyncStoppeeByHandler
| [junit] main 08:20:36,486 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] main 08:20:36,712 INFO [UnitTestCase] ###### starting test testStopStartConsumerAsyncASync
| [junit] main 08:20:36,713 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] main 08:20:36,933 INFO [UnitTestCase] ###### starting test testStopStartMultipleConsumers
| [junit] main 08:20:36,934 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] consumer = messages in buffer = 2
| [junit] consumer2 = messages in buffer = 4
| [junit] consumer3 = messages in buffer = 5
| [junit] Thread-29 08:20:36,962 WARN [RemotingConnectionImpl] Connection failure has been detected The connection has been closed by the server:102
| [junit] Thread-29 08:20:36,962 WARN [RemotingConnectionImpl] Connection failure has been detected The connection has been closed by the server:102
| [junit] main 08:20:36,964 INFO [UnitTestCase] ###### starting test testStopStartAlreadyStartedSession
| [junit] main 08:20:36,964 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] main 08:20:36,985 INFO [UnitTestCase] ###### starting test testStopAlreadyStoppedSession
| [junit] main 08:20:36,986 WARN [SecurityStoreImpl] It has been detected that the cluster admin password which is used to replicate management operation from one node to the other has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
| [junit] Tests run: 9, Failures: 0, Errors: 1, Time elapsed: 12.451 sec
| [junit] Test org.jboss.messaging.tests.integration.client.ClientSessionStopStartTest FAILED
|
This is one of the Failures that will eventually happen:
|
| Connection is destroyed
|
| MessagingException[errorCode=2 message=Connection is destroyed]
| at org.jboss.messaging.core.remoting.impl.RemotingConnectionImpl$ChannelImpl.sendBlocking(RemotingConnectionImpl.java:1072)
| at org.jboss.messaging.core.client.impl.ClientSessionImpl.stop(ClientSessionImpl.java:627)
| at org.jboss.messaging.tests.integration.client.ClientSessionStopStartTest.testStopStartConsumerAsyncSync(ClientSessionStopStartTest.java:317
|
I have also seen another Failure.... Let me try to reproduce the other one?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221568#4221568
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221568
15 years, 1 month
[Design of JBoss ESB] - Re: Smooks JavaBinding
by tfennelly
I don't think you can do this directly, but it wouldn't be hard to get it to work with the help of a little Groovy scripting to manually wire the address records into the address Map.
Also, you can probably abreviate the binding config for mapping the csv-record set data into the Map.
Here's what it would look like (untested)...
| <jb:bindings beanId="addresses" class="java.util.HashMap" createOnElement="csv-set" />
|
| <jb:bindings beanId="addressRecord" class="java.util.HashMap" createOnElement="csv-record">
| <!-- Omit the property + use a wildcard selector => Smooks will use the element name as the Map key -->
| <jb:value data="csv-record/*" />
| </jb:bindings>
|
| <g:groovy executeOnElement="csv-record">
| <g:script>
| <!--
| // Manually wire each addressRecord into the address Map...
| Map addresses = BeanRepository.getInstance(executionContext).getBean("addresses");
| Map addressRecord = BeanRepository.getInstance(executionContext).getBean("addressRecord");
|
| addresses.put(addressRecord.ADDR_ID, addressRecord);
| -->
| </g:script>
| </g:groovy>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221550#4221550
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221550
15 years, 1 month
[Design of EJB 3.0] - Re: WS EJB invocation
by semanticLance
I am seeing this error in 5.0.0.GA with an ear that deployed successfully in 4.2.0.GA.
Any advice for tracking down the offending code?
| 08:48:41,910 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/lwbyrd/pkg/jboss-5.0.0.GA/server/default/deploy/blackbook.ear state=PreReal mode=Manual requiredState=Real
| org.jboss.deployers.spi.DeploymentException: java.lang.NullPointerException: name cannot be null
| at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:100)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
| at org.jboss.Main.boot(Main.java:209)
| at org.jboss.Main$1.run(Main.java:547)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.NullPointerException: name cannot be null
| at javax.management.ObjectName.construct(ObjectName.java:342)
| at javax.management.ObjectName.<init>(ObjectName.java:1314)
| at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:96)
| ... 21 more
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221544#4221544
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221544
15 years, 1 month
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: bug in session.rollback()
by timfox
Probably the real bug is that it's not using the queue from the reference, it's using the owner queue of the inner class, i.e. something like:
| void postRollback(LinkedList<MessageReference> refs) throws Exception
| {
| synchronized (this)
| {
| for (MessageReference ref : refs)
| {
| ServerMessage msg = ref.getMessage();
|
| if (!scheduledDeliveryHandler.checkAndSchedule(ref, backup))
| {
| messageReferences.addFirst(ref, msg.getPriority());
| }
| }
|
| deliver();
| }
| }
|
Should really be:
| void postRollback(LinkedList<MessageReference> refs) throws Exception
| {
| synchronized (this)
| {
| for (MessageReference ref : refs)
| {
| ServerMessage msg = ref.getMessage();
|
| if (!scheduledDeliveryHandler.checkAndSchedule(ref, backup))
| {
| ref.getQueue().messageReferences.addFirst(ref, msg.getPriority());
| }
| }
|
| deliver();
| }
| }
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221521#4221521
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221521
15 years, 1 month