[JBoss Remoting] - unable to call EJB services in 4.0.5 installation from 5.1
by max Shestopalov
max Shestopalov [http://community.jboss.org/people/mshestopalov] created the discussion
"unable to call EJB services in 4.0.5 installation from 5.1"
To view the discussion, visit: http://community.jboss.org/message/645472#645472
--------------------------------------------------------------
Hi,
For a while we had 2 instances of 4.0.5 running where instance A was calling EJB services of instance B. We upgraded instance A to 5.1 and at that point started getting the InvokationException with the serial number mismatch between classes in the 2 different versions of jbossas-client.jar.
After doing a little research I started bringing up instance A with the property -Djboss.remoting.pre_2_0_compatible=true and the error I started seeing was
java.lang.Exception: Can not make remoting client invocation due to
not being connected to server.
org.jboss.remoting.Client.invoke(Client.java:1729)
org.jboss.remoting.Client.invoke(Client.java:629)
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
$Proxy351.searchForExperiments(Unknown Source)
gov.nih.nci.caintegrator2.external.caarray.CaArrayUtils.getExperiment(CaArrayUtils.java:168)
When I googled this I found a seemingly helpful thread speaking about
the new req in remoting 2.x that connect() be called before invoke()
and how this did not use to be required in remoting 1.x
here is the thread: http://community.jboss.org/message/368917#368917 http://community.jboss.org/message/368917#368917
but I actually can't figure out how we are doing this since
we aren't writing a client and invoking from the container.
also, fyi, as a test upgrading instance B to 5.1 as well... everything works fine.
Any help would be greatly appreciated.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/645472#645472]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[JNDI and Naming] - JNDI binding in extension module READONLY exception
by hellen-z
hellen-z [http://community.jboss.org/people/hellen-z] created the discussion
"JNDI binding in extension module READONLY exception"
To view the discussion, visit: http://community.jboss.org/message/645537#645537
--------------------------------------------------------------
Hi,
My component is deployed as an extension module. And I cannot use EJB annotation for resource injection since only web profile can be used.
So I try to do binding calling
new InitialContext().bind(....),
and I got excetion
JBAS011859: Naming context is read-only: java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:118) [jboss-as-naming-7.1.0.CR1.jar:7.1.0.CR1]
at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:53) [jboss-as-naming-7.1.0.CR1.jar:7.1.0.CR1]
at org.jboss.as.naming.NamingContext.bind(NamingContext.java:220) [jboss-as-naming-7.1.0.CR1.jar:7.1.0.CR1]
at org.jboss.as.naming.InitialContext.bind(InitialContext.java:146) [jboss-as-naming-7.1.0.CR1.jar:7.1.0.CR1]
at org.jboss.as.naming.NamingContext.bind(NamingContext.java:229) [jboss-as-naming-7.1.0.CR1.jar:7.1.0.CR1]
Result is the same if I use either *org.jboss.as.naming.InitialContext* or *javax.naming.InitialContext*
Could you give any suggestions what I need to to?
Thanks very much!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/645537#645537]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[Beginner's Corner] - Soap over Jms - Error: Insufficient configuration for Conduit
by ale2011
ale2011 [http://community.jboss.org/people/ale2011] created the discussion
"Soap over Jms - Error: Insufficient configuration for Conduit"
To view the discussion, visit: http://community.jboss.org/message/645269#645269
--------------------------------------------------------------
Hello,
I've been following this documentation for SOAP over JMS: https://docs.jboss.org/author/display/JBWS/SOAP+over+JMS https://docs.jboss.org/author/display/JBWS/SOAP+over+JMS
I'm able to get the server to work but after when I implemented the client, I tried to run it and I have this error:
Jan 8, 2012 7:51:05 PM org.apache.cxf.service.factory.ReflectionServiceFactoryBean buildServiceFromWSDL
INFO: Creating Service {http://soapjms.rd.nsrr.swim.faa.gov/}SoapJmsWeatherImpl from WSDL: <PATH_TO_WSDL>
Invoking getForecast...
Jan 8, 2012 7:51:10 PM org.apache.cxf.phase.PhaseInterceptorChain doDefaultLogging
WARNING: Interceptor for {http://soapjms.rd.nsrr.swim.faa.gov/}SoapJmsWeatherImpl#{http://soapjms.rd.nsrr.swim.faa.gov/}GetForecast has thrown exception, unwinding now
org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Conduit. Did you configure a
<jms:conduit name="{http://soapjms.rd.nsrr.swim.faa.gov/}SoapJmsWeatherImplPort.jms-conduit"> and set the
jndiConnectionFactoryName ?
at org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:106)
at org.apache.cxf.transport.jms.JMSConduit.prepare(JMSConduit.java:102)
at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:46)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:484)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:414)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:317)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:269)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
at $Proxy25.getForecast(Unknown Source)
at gov.faa.swim.nsrr.rd.soapjms.Main.main(Main.java:49)
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Insufficient configuration for Conduit. Did you configure a
<jms:conduit name="{http://soapjms.rd.nsrr.swim.faa.gov/}SoapJmsWeatherImplPort.jms-conduit"> and set the
jndiConnectionFactoryName ?
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
at $Proxy25.getForecast(Unknown Source)
at gov.faa.swim.nsrr.rd.soapjms.Main.main(Main.java:49)
Caused by: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Conduit. Did you configure a
<jms:conduit name="{http://soapjms.rd.nsrr.swim.faa.gov/}SoapJmsWeatherImplPort.jms-conduit"> and set the
jndiConnectionFactoryName ?
at org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:106)
at org.apache.cxf.transport.jms.JMSConduit.prepare(JMSConduit.java:102)
at org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:46)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:484)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:414)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:317)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:269)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
... 2 more
I have created a cxf.xml file that contains the jms:conduit and jms:destination (below), and put it in the /WEB-INF/ directory of my server .WAR file. But somehow JBoss does not read that file.
...
<jms:conduit name="{http://soapjms.rd.nsrr.swim.faa.gov/}SoapJmsWeatherImplPort.jms-conduit">
<jms:address destinationStyle="queue"
jndiConnectionFactoryName="java:activemq/QueueConnectionFactory"
jndiDestinationName="java:activemq/queue/GetForecastRequestQueue"
jndiReplyDestinationName="java:activemq/queue/GetForecastResponseQueue">
<jms:JMSNamingProperty name="java.naming.factory.initial"
value="org.apache.activemq.jndi.ActiveMQInitialContextFactory" />
<jms:JMSNamingProperty name="java.naming.provider.url" value="vm://localhost" />
</jms:address>
</jms:conduit>
<jms:destination name="{http://soapjms.rd.nsrr.swim.faa.gov/}SoapJmsWeatherImplPort.jms-destination">
<jms:address destinationStyle="queue"
jndiConnectionFactoryName="java:activemq/QueueConnectionFactory"
jndiDestinationName="java:activemq/queue/GetForecastRequestQueue"
jndiReplyDestinationName="java:activemq/queue/GetForecastResponseQueue">
<jms:JMSNamingProperty name="java.naming.factory.initial"
value="org.apache.activemq.jndi.ActiveMQInitialContextFactory" />
<jms:JMSNamingProperty name="java.naming.provider.url" value="vm://localhost" />
</jms:address>
</jms:destination>
...
Here is my client:
package gov.faa.swim.nsrr.rd.soapjms;
import java.net.URL;
import javax.xml.namespace.QName;
import org.apache.cxf.Bus;
import org.apache.cxf.BusFactory;
import org.apache.cxf.interceptor.LoggingInInterceptor;
import org.apache.cxf.jaxws.JaxWsProxyFactoryBean;
public final class Main {
private static final QName SERVICE_NAME = new QName("http://soapjms.rd.nsrr.swim.faa.gov/", "SoapJmsWeatherImpl");
private Main() { }
public static void main(String args[]) throws Exception {
URL wsdlURL = SoapJmsWeatherImpl.WSDL_LOCATION;
Bus bus = BusFactory.newInstance().createBus();
BusFactory.setThreadDefaultBus(bus);
try {
SoapJmsWeatherImpl service = new SoapJmsWeatherImpl(wsdlURL, SERVICE_NAME);
System.out.println("===== Interacting with JMS endpoint ======");
SoapJmsWeatherImplPortType proxy = (SoapJmsWeatherImplPortType) service.getSoapJmsWeatherImplPort();
System.out.println("\nInvoking getForecast...");
proxy.getForecast("Philadelphia");
}
finally {
bus.shutdown(true);
}
System.exit(0);
}
}
Could someone guide me to the right direction to get this to work? Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/645269#645269]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[JBoss Messaging] - JBM clients hangs when creating connections/sessions
by Daniel Dumitrescu
Daniel Dumitrescu [http://community.jboss.org/people/danezu] created the discussion
"JBM clients hangs when creating connections/sessions"
To view the discussion, visit: http://community.jboss.org/message/644597#644597
--------------------------------------------------------------
Hello guys
We're facing a problem with JMS remote clients hanging like forever when trying to create connections/sessions on a JBoss Messaging 1.4.5.SP1 on JBoss 4.2.3 GA
The setup is the following:
- JBoss Servers:
# 3 JBoss 4.2.3 GA set up in cluster, with the same multi-cast IP address and partition name
# JBoss Messaging 1.4.5 SP1 installed on each one of them, with one queue and 5 topics, all clustered and with durable subscriptions
# MySQL 5.5.9 as persistence layer for JBM
# persisten messages needed, no message should be ever lost
- remote clients
# simple clients that looks up for {code}XAConnectionFactory{code}, and send every 30 secs more than one message, every time with JNDI lookup, create connection & session (all are closed in the finally clause). One addition: on the client side is made XA resource enlisting with the remote target queue and the transaction is managed by hand on both client and JBM side.
The load from the client side to the server is not so high, like 10,000 - 20,000 messages per day, but after 8-10 days the cluster gets unresponsive to new JMS remote connections, and the clinet threads are hanging. The local message processing, i.e. on each node on the topics works, which led me to the fact that can be a problem with JBoss Remoting
The client threads are locking in this point:
{code}
Thread: JMS SessionPool Worker-0 : priority:5, demon:true, threadId:228, threadState:RUNNABLE, lockName:null
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
java.io.BufferedInputStream.read(BufferedInputStream.java:237)
java.io.FilterInputStream.read(FilterInputStream.java:66)
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1077)
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:682)
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458)
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
org.jboss.remoting.Client.invoke(Client.java:1925)
org.jboss.remoting.Client.invoke(Client.java:786)
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:178)
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:80)
org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
org.jboss.jms.client.JBossConnectionFactory.createXAQueueConnection(JBossConnectionFactory.java:142)
{code}
Have anyone encountered this behavior?
Regards,
Daniel
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/644597#644597]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months