June 2007 - jboss-user - Jboss List Archives

[JBoss Messaging] - Problems with concurrent.jar

by kkoster

I know this is not directly related to JBoss Messaging, but since it came up during its usage I thought this would be a good place to post this problem. It seems that the ConcurrentHashMap's inner Segment class is not marked as Serializable (it is in the Doug Lea's source code) and is causing problems with messaging. The concurrent.jar that is being used is in the latest AOP (1.5.5.GA) release in the either the lib or lib-50 directory. The version in the lib directory of JAS is marked as serializable and when switching to that version, the exceptions stopped. Below is a stack trace of the exceptions being thrown by the messaging client when using the AOP version of concurrent.jar: | 11:41:03,751 ERROR [JMSWireFormat] Failed to write packet | java.io.NotSerializableException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) | at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) | at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391) | at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1170) | 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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80) | at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:969) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:557) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283) | at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117) | at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:398) | at org.jboss.remoting.Client.setupClientLease(Client.java:1541) | at org.jboss.remoting.Client.connect(Client.java:1441) | at org.jboss.remoting.Client.connect(Client.java:444) | at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:271) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:146) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83) | at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) | at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:131) | 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:121) | at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java) | at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) | at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87) | at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82) | at org.kdr.jms.BasicContentSynchManager.getConnection(BasicContentSynchManager.java:93) | at org.kdr.jms.BasicContentSynchManager.start(BasicContentSynchManager.java:191) | at org.kdr.jms.TestContentSynchManager.<init>(TestContentSynchManager.java:41) | at org.kdr.jms.TestContentSynchManager.main(TestContentSynchManager.java:63) | 11:41:03,766 ERROR [SocketClientInvoker] Got marshalling exception, exiting | java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) | at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) | at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391) | at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1170) | 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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80) | at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:969) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:557) | at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283) | at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117) | at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:398) | at org.jboss.remoting.Client.setupClientLease(Client.java:1541) | at org.jboss.remoting.Client.connect(Client.java:1441) | at org.jboss.remoting.Client.connect(Client.java:444) | at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:271) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:146) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83) | at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) | at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:131) | 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:121) | at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java) | at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) | at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87) | at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82) | at org.kdr.jms.BasicContentSynchManager.getConnection(BasicContentSynchManager.java:93) | at org.kdr.jms.BasicContentSynchManager.start(BasicContentSynchManager.java:191) | at org.kdr.jms.TestContentSynchManager.<init>(TestContentSynchManager.java:41) | at org.kdr.jms.TestContentSynchManager.main(TestContentSynchManager.java:63) | 11:41:03,766 WARN [LeasePinger] LeasePinger[SocketClientInvoker[7981d5, bisocket://10.10.100.10:4457](aa2s2v-2r2fch-f3helqsj-1-f3helrmh-5)] failed to ping to server: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: | java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058842#4058842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058842

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: java.lang.UnsupportedOperationException

by rmemoria

After spending a long time trying to upgrade from one SEAM version to another I found a "quick" way: 1 - Rename your eclipse project; 2 - With the new SEAM version, use SEAM-GEN to generate a project with the same name of the previous one; 3 - Copy the .xhtml pages, and source dir from the renamed project to the new one; 4 - Copy manually any changes made in components.xml and pages.xml to the new project It saves me a lot of time. Regards, Ricardo Memoria View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058841#4058841 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058841

18 years, 9 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: JBoss Virtual Host

by sepgs2004

I do not know if you ever looked into this.. Might be helpful http://evolutionnext.com/blog/2005/09/05/1125954329320.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058840#4058840 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058840

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: InputText value being cached

by texan

As a followup, I had trouble implementing their workaround (from the Jira bug). I was cancelling from a popup window, trying to end the conversation, and reload the parent window. For some reason, when I tried to do this from the action listener, my parent window would hang. I got it working by implementing both a listener and an action for the cancel button. The listener executes the workaround (clearing the submitted values in the UIComponents), while the action ends the conversation and triggers the parent window to reload. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058836#4058836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058836

18 years, 9 months

1
0
0 / 0

[JBossCache] - Re: jboss cache + glassfish - problem using GenericTransacti

by bstansberry＠jboss.com

Seems you've found a bug: http://jira.jboss.com/jira/browse/JBCACHE-1114. Unfortunately, there's no simple workaround. As for the javax.management.InstanceNotFoundException, there is a solution for that. From pt.iol.services.cache.CacheContext, don't call TreeCache.stop(). Call TreeCache.stopService(). Make equivalent changes for any call to create(), start() or destroy(). In JBC 1.x, create()/start()/stop()/destroy() only work properly when JBC is deployed inside JBoss AS, while createService()/startService()/stopService()/destroyService() will do what you want. See http://jira.jboss.com/jira/browse/JBCACHE-1001 and related forum thread for a discussion on why that is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058835#4058835 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058835

18 years, 9 months

1
0
0 / 0

[Beginners Corner] - Limited-scope Client classpath?

by rob.stryker＠jboss.com

Hi... I'm trying to use JMX to get a value / attribute, specifically something like using twiddle to get get "jboss.system:type=Server" Started I'm having problems even getting an initial context properly. I'm wondering what's the limited number of jars I'd need to get the following to work. I don't want to include jbossall-client, for example. public static void main(String[] args) { InitialContext ctx; Properties props = new Properties(System.getProperties()); props.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); props.put("java.naming.provider.url","jnp://localhost:1099"); props.put("java.naming.factory.url.pkgs","org.jboss.naming:org.jnp.interfaces"); try { ctx = new InitialContext(props); Object obj = ctx.lookup("jmx/invoker/RMIAdaptor"); ctx.close(); System.out.println(obj); } catch( NamingException ne ) { ne.printStackTrace(); } } If I include jbossall-client on the classpath, it works fine. But if I only include jnp-client.jar, I get missing classes for jboss Logging. Any advice on using JMX in this fashion will be appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058832#4058832 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058832

18 years, 9 months

1
0
0 / 0

[Beginners Corner] - Re: Problems with the <jar-file> element in the persistence.

by Marcos_APS

"rob.stryker(a)jboss.com" wrote : An entity bean is a type of enterprise java bean. I don't believe that should go in the lib folders. This file (urca.jar) doesn't have only entity beans. It also has utility classes that could be used in all applications. So, where do you suggest me to place it instead of the lib directory? A place where I can point to it in the <jar-file> element. Is there a way to a jar file located in the lib directory from the <jar-file> element? That was the initial point of this discussion. If there's no way, I would be satisfied with another properly place to put the jar file that allowed me to reference it from the <jar-file>. Marcos View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058827#4058827 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058827

18 years, 9 months

1
0
0 / 0

[Clustering/JBoss] - Re: JGroups Transfer Rate with UDP really slow

by seniorfrog

Check out the performance test results on the JGroups website. http://www.jgroups.org/javagroupsnew/docs/Perftest.html I imagine it has something to do with flow control (UDP doesn't provide very good flow control, and therefore packets get lost). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058825#4058825 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058825

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: problems wih getters

by dajevtic

Post at least some code. Help us help you! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058823#4058823 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058823

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - dvd store question

by kgoedert

In the dvd store example in the admin page there is this <s:button action="#{accept.viewTask}" taskInstance="#{task}" value="Review"/> In the AcceptAction there is an injection of @In Long orderId; and in the viewTask method is the orderId is used to do the search. My question is, how is orderId injected? Or, which property on the admin page sets the value of orderId? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058821#4058821 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058821

18 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2007