[JBoss Messaging] - 1.0.1CR5 Not Backwards Compatible
by OliverHrdz
Luckily, my project has not yet upgraded production from JBossMQ to Messaging. We're back now to testing a new version of JBoss for JMS, and I found that CR5 is not backwards compatible. My 1.0.1CR4 client could not connect to the updated Messaging server, logging the following error:
anonymous wrote : java.lang.ExceptionInInitializerError
| at sun.reflect.GeneratedSerializationConstructorAccessor50.newInstance(Unknown Source)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
| at org.jboss.serial.classmetamodel.ClassMetaData.newInstance(ClassMetaData.java:337)
| at org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:239)
| at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
| at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
| at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:634)
| at org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353)
| at org.jboss.serial.persister.RegularObjectPersister.defaultRead(RegularObjectPersister.java:273)
| at org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:241)
| at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
| at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
| at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:634)
| at org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353)
| at org.jboss.serial.persister.RegularObjectPersister.defaultRead(RegularObjectPersister.java:273)
| at org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:241)
| at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
| at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
| at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:634)
| at org.jboss.serial.io.JBossObjectInputStream.readObjectOverride(JBossObjectInputStream.java:163)
| at java.io.ObjectInputStream.readObject(ObjectInputStream.java:343)
| at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:132)
| at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
| at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:422)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:477)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:351)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:116)
| at org.jboss.remoting.Client.invoke(Client.java:612)
| at org.jboss.remoting.Client.invoke(Client.java:604)
| at org.jboss.jms.client.delegate.DelegateSupport.invoke(DelegateSupport.java:112)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
| at org.jboss.jms.client.container.StateCreationAspect.handleCreateSessionDelegate(StateCreationAspect.java:101)
| at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect1.invoke(StateCreationAspect1.java)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
| at org.jboss.jms.client.container.ConnectionAspect.handleCreateSessionDelegate(ConnectionAspect.java:164)
| 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:585)
| at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:130)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:134)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
| at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
| at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate.createSessionDelegate(ClientConnectionDelegate.java)
| at org.jboss.jms.client.JBossConnection.createSessionInternal(JBossConnection.java:255)
| at org.jboss.jms.client.JBossConnection.createQueueSession(JBossConnection.java:165)
| at mil.navy.erm.jms.JMSConnection$QueueSessionRequest.createSession(JMSConnection.java:959)
| at mil.navy.erm.jms.JMSConnection$QueueSessionRequest.createSession(JMSConnection.java:931)
| at mil.navy.erm.jms.JMSConnection$SessionRequest.requestSession(JMSConnection.java:899)
| at mil.navy.erm.jms.JMSConnection.getQueueSession(JMSConnection.java:417)
| at InboundTransProcessor.run(InboundTransProcessor.java:95)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.RuntimeException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
| at org.jboss.aop.advice.AdviceFactory.create(AdviceFactory.java:72)
| at org.jboss.aop.Advisor.createInterceptorChain(Advisor.java:646)
| at org.jboss.aop.Advisor.pointcutResolved(Advisor.java:916)
| at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:678)
| at org.jboss.aop.ClassAdvisor.createInterceptorChains(ClassAdvisor.java:604)
| at org.jboss.aop.ClassAdvisor.access$300(ClassAdvisor.java:82)
| at org.jboss.aop.ClassAdvisor$1.run(ClassAdvisor.java:299)
| at java.security.AccessController.doPrivileged(Native Method)
| at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:271)
| at org.jboss.aop.AspectManager.initialiseClassAdvisor(AspectManager.java:587)
| at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:575)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.(ClientSessionDelegate.java)
| ... 57 more
| Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
| at java.util.ArrayList.RangeCheck(ArrayList.java:546)
| at java.util.ArrayList.get(ArrayList.java:321)
| at org.jboss.aop.advice.PerVmAdvice.generateInterceptor(PerVmAdvice.java:118)
| at org.jboss.aop.advice.PerVmAdvice.generateOptimized(PerVmAdvice.java:52)
| at org.jboss.aop.advice.AdviceFactory.create(AdviceFactory.java:68)
| ... 68 more
|
I'm suspecting from the above stack trace the issue is with Remoting. I notice the jboss-remoting.jar files are different in each version of the messaging.sar. Is this a Remoting issue?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975854#3975854
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975854
19 years, 7 months
[Installation, Configuration & Deployment] - how does one use custom properties for define ports in the b
by mlanza
I am in the process of designing a scripted configuration build process so that I can quickly add servers to existing jboss app server (version 4.0.3SP1) binary installations on my Linux servers. My intention was to use the property-service by creating a local.properties file in the root of the configuration [e.g. $JBOSS_ROOT/server/appserver01/conf/local.properties] and maintain a separate bindings.xml file per configuration [e.g. $JBOSS_ROOT/server/appserver01/bindings.xml]. the variables defined in the local.properties file would be used in place of the static ports in the bindings.xml file.
I am having trouble getting this to work as it seems that jboss is no processing the local.properties early enough in the startup process since I get a number format exception once it reads the bindings.xml file:
14:41:19,617 INFO [ServiceBindingManager] Using StoreURL: file:/usr/local/jboss/server/test01/bindings.xml
14:41:19,635 WARN [ServiceConfigurator] Failed to apply service binding override
java.lang.NumberFormatException: For input string: "${jboss.ports.Naming}"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975852#3975852
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975852
19 years, 7 months