[JNDI/Naming/Network] - Problem getting Datasource vi JNDI
by mjais
hello
I am trying to get the Quartz scheduler running:
I have a local jboss (4.0.3) running on my machine and configured the Quartz datasource.
via the JBoss JMX console I can see that the datasource is bound:
java: Namespace
+- jaas (class: javax.naming.Context)
.............
+- jdbc (class: org.jnp.interfaces.NamingContext)
| +- QuartzDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
| +- QuartzNoTxDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
..............
I wrote the following client programme to access the datasource:
class ContextTest {
public static DataSource getDataSource(String dataSourceJndiName) {
DataSource dataSource = null;
Properties prop = new Properties();
prop.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
prop.put(Context.URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces");
prop.put(Context.PROVIDER_URL, "jnp://localhost:1099");
try {
Context ctx = new InitialContext(prop);
dataSource = (DataSource) ctx.lookup(dataSourceJndiName);
} catch (ClassCastException cce) {
cce.printStackTrace();
} catch (NamingException ne) {
ne.printStackTrace();
}
return dataSource;
}
public static void main(String[] args) {
DataSource ds = getDataSource("java:comp/env/jdbc/QuartzDS");
System.out.println(ds.toString());
}
}
and I get this error:
javax.naming.NameNotFoundException: comp not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:514)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:522)
at org.jnp.server.NamingServer.getObject(NamingServer.java:528)
at org.jnp.server.NamingServer.lookup(NamingServer.java:252)
I also tried many other combinations for the JNDI Name, but I never managed
to get the Datasource.
calling the code from within a JSF application (deployed on the JBoss where the
Quartz datasource is) doesn't work either.
any idea what's wrong here ?
Markus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000890#4000890
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000890
19 years, 3 months
[JBoss Messaging] - Re: JMS Exceptions / Mismatch of JBossSerialization version
by timfox
rtm-
Can you confirm a couple of things for me:
In remoting-service.xml, you should have something like:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=socket"
| display-name="Socket transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="socket">
| <attribute name="marshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
| <!-- Serialization type must be jms - do not change! -->
| <attribute name="serializationtype" isParam="true">jms</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4457</attribute>
| <attribute name="leasePeriod">10000</attribute>
| <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| <depends>jboss.messaging:service=NetworkRegistry</depends>
| </mbean>
|
Can you verify you are specifying the clientSocketClass and serverSocketClass attributes as above?
Secondly, if you are using ServiceBindingManager to map your ports, can you verify, in your bindings xml file, you have something like:
| <service-config name="jboss.messaging:service=Connector,transport=socket"
| delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
| <delegate-config>
| <attribute name="Configuration"><![CDATA[
| <config>
| <invoker transport="socket">
| <attribute name="marshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.server.remoting.JMSWireFormat</attribute>
| <!-- Serialization type must be jms - do not change! -->
| <attribute name="serializationtype" isParam="true">jms</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4457</attribute>
| <attribute name="leasePeriod">10000</attribute>
| <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| </invoker>
| <handlers>
| <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
| </handlers>
| </config>
| ]]>
| </attribute>
| </delegate-config>
|
| <binding port="7544"/>
| </service-config>
|
The remoting config in your bindings.xml file should exactly match the config in messaging-service.xml.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000884#4000884
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000884
19 years, 3 months
[JBoss Messaging] - Re: JMS Exceptions / Mismatch of JBossSerialization version
by rtm333
I have raised the log level, not (yet) to TRACE, but to DEBUG. Even this revealed some additional clues:
Client side:
| 11:52:30,669 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:30,669 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:30,669 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:30,669 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:30,669 DEBUG [MicroRemoteClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@53ecec
| 11:52:30,685 DEBUG [MicroRemoteClientInvoker] disconnect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@53ecec
| 11:52:31,169 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:31,169 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:31,169 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:31,169 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:31,169 DEBUG [MicroRemoteClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@10eb6ae
| 11:52:31,185 DEBUG [MicroRemoteClientInvoker] disconnect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@10eb6ae
| 11:52:32,670 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:32,670 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:32,670 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:32,670 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:32,670 DEBUG [MicroRemoteClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@1cba031
| 11:52:33,373 DEBUG [MicroRemoteClientInvoker] disconnect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@1cba031
| 11:52:33,373 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:33,373 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:33,373 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:33,373 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:33,373 DEBUG [MicroRemoteClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@1220575
| 11:52:33,483 DEBUG [MicroRemoteClientInvoker] disconnect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@1220575
| 11:52:34,670 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:34,670 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:34,670 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:34,670 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:34,670 DEBUG [MicroRemoteClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@12e712f
| 11:52:35,936 ERROR [SocketClientInvoker] Got marshalling exception, exiting
| java.net.SocketTimeoutException: Read timed out
| at java.net.SocketInputStream.socketRead0(Native Method)
| at java.net.SocketInputStream.read(SocketInputStream.java:129)
| at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
| at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
| at java.io.FilterInputStream.read(FilterInputStream.java:66)
| at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:193)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:531)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:363)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125)
| at org.jboss.remoting.ConnectionValidator.checkConnection(ConnectionValidator.java:184)
| at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:114)
| at java.util.TimerThread.mainLoop(Timer.java:512)
| at java.util.TimerThread.run(Timer.java:462)
| 11:52:35,936 DEBUG [ConnectionValidator] ConnectionValidator could not successfully ping server (InvokerLocator [socket://xxx123:11107/?clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&serializationtype=jboss&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]
| 11:52:35,936 DEBUG [MicroRemoteClientInvoker] disconnect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@12e712f
| 11:52:35,952 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:35,952 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:35,952 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:35,952 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:35,952 DEBUG [MicroRemoteClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@5ce0fe
| 11:52:35,983 ERROR [ConnectionAspect] Caught exception from connection
| java.lang.Exception: Could not connect to server.
| at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:117)
| at java.util.TimerThread.mainLoop(Timer.java:512)
| at java.util.TimerThread.run(Timer.java:462)
| E yyy123 instance_1 12.01.2007 11:52:35.983 TopicReceiver.onException: Received JMSException for priceTopic: Throwable received from underlying connection
| 1 yyy123 instance_1 12.01.2007 11:52:36.046 javax.jms.JMSException: Throwable received from underlying connection (Stack Trace following)
| javax.jms.JMSException: Throwable received from underlying connection
| at org.jboss.jms.client.container.ConnectionAspect.handleConnectionException(ConnectionAspect.java:203)
| at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:139)
| 11:52:36,749 DEBUG [MicroRemoteClientInvoker] disconnect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@5ce0fe
| 11:52:37,952 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:37,952 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:37,952 DEBUG [MicroSocketClientInvoker] Setting ClientSocket class name to: org.jboss.jms.client.remoting.ClientSocketWrapper
| 11:52:37,952 DEBUG [SocketClientInvoker] Setting SocketClientInvoker::timeout to: 1000
| 11:52:37,952 DEBUG [MicroRemoteClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@cc8a48
| 11:52:38,953 DEBUG [ConnectionValidator] ConnectionValidator could not successfully ping server (InvokerLocator [socket://xxx123:11107/?clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&serializationtype=jboss&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]
| 11:52:38,953 DEBUG [MicroRemoteClientInvoker] disconnect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@cc8a48
| 11:52:38,953 ERROR [ConnectionAspect] Caught exception from connection
| java.lang.Exception: Could not connect to server.
| at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:117)
| at java.util.TimerThread.mainLoop(Timer.java:512)
| at java.util.TimerThread.run(Timer.java:462)
| E yyy123 instance_1 12.01.2007 11:52:38.953 TopicReceiver.onException: Received JMSException for paramTopic: Throwable received from underlying connection
| 1 yyy123 instance_1 12.01.2007 11:52:39.000 javax.jms.JMSException: Throwable received from underlying connection (Stack Trace following)
| javax.jms.JMSException: Throwable received from underlying connection
| at org.jboss.jms.client.container.ConnectionAspect.handleConnectionException(ConnectionAspect.java:203)
| at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:139)
|
Server side:
2007-01-12 11:53:13,834 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] Failed to accept socket connection
| java.lang.reflect.InvocationTargetException
| at sun.reflect.GeneratedConstructorAccessor43.newInstance(Unknown Source)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
| at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:216)
| at org.jboss.remoting.transport.socket.ServerThread.wakeup(ServerThread.java:275)
| at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:604)
| at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:515)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.net.SocketException: Connection reset
| at java.net.SocketInputStream.read(SocketInputStream.java:168)
| at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
| at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
| at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
| at java.io.FilterInputStream.read(FilterInputStream.java:90)
| at org.jboss.serial.io.JBossObjectInputStream.checkSignature(JBossObjectInputStream.java:110)
| at org.jboss.serial.io.JBossObjectInputStream.<init>(JBossObjectInputStream.java:94)
| at org.jboss.remoting.serialization.impl.jboss.JBossSerializationManager.createInput(JBossSerializationManager.java:59)
| at org.jboss.jms.server.remoting.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:110)
| at org.jboss.jms.client.remoting.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:116)
| at org.jboss.jms.client.remoting.ClientSocketWrapper.<init>(ClientSocketWrapper.java:67)
| at org.jboss.jms.server.remoting.ServerSocketWrapper.<init>(ServerSocketWrapper.java:64)
| ... 8 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000876#4000876
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000876
19 years, 3 months
[JBossCache] - Re: Problem with JBossCache configuration
by LGSW_Sam
Now I am also getting these...
| 13:56:48,033 WARN [TxInterceptor] Rolling back, exception encountered
| java.lang.NullPointerException
| at org.jboss.cache.interceptors.OptimisticNodeInterceptor.invoke(OptimisticNodeInterceptor.java:68)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.OptimisticCreateIfNotExistsInterceptor.invoke(OptimisticCreateIfNotExistsInterceptor.java:69)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.OptimisticValidatorInterceptor.invoke(OptimisticValidatorInterceptor.java:75)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.OptimisticLockingInterceptor.invoke(OptimisticLockingInterceptor.java:122)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.InvalidationInterceptor.invoke(InvalidationInterceptor.java:60)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:345)
| at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:156)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:183)
| at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5520)
| at org.jboss.cache.TreeCache.remove(TreeCache.java:3742)
| at org.jboss.cache.TreeCache.remove(TreeCache.java:3297)
| at org.hibernate.cache.OptimisticTreeCache.writeLoad(OptimisticTreeCache.java:76)
| at org.hibernate.cache.TransactionalCache.put(TransactionalCache.java:55)
| at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:156)
| at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:842)
| at org.hibernate.loader.Loader.doQuery(Loader.java:717)
| at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
| at org.hibernate.loader.Loader.loadEntity(Loader.java:1851)
| at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48)
| at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42)
| at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2992)
| at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:395)
| at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:375)
| at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139)
| at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195)
| at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103)
| at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878)
| at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:846)
| at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:557)
| at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:196)
| at org.hibernate.collection.PersistentSet.initializeFromCache(PersistentSet.java:124)
| at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35)
| at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130)
| at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48)
| at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1716)
| at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
| at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
| at org.hibernate.collection.PersistentSet.iterator(PersistentSet.java:163)
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000874#4000874
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000874
19 years, 3 months
[JBoss AOP] - Re: Determining who made the original call
by kabir.khan＠jboss.com
"aleksab" wrote : Where is the connection from ie. the domain "Stateless Bean" to the annotation @Stateless made?
It is hardcoded. If you also use @Clustered it uses "Clustered Stateless Bean" (or whatever it is called), which again is hardcoded. For any other domains, use @AspectDomain.
a)
*@Local must be running within JBoss AS and has no interceptors. The container will thus be running in the same thread as the caller.
*@Remote obviously can run outside, it has a stack of client interceptors. It needs to put the info into the invocation metadata so that can be picked up on the server.
b)
I'd add a new stack, copying the information from StatelessSessionClientInterceptors. and adding your interceptor in there somewhere and use @RemoteBinding(interceptorStack="MyCustomSLSBClientInterceptorStack")
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000872#4000872
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000872
19 years, 3 months