[JBoss Web Services] - can't call a .NET web service ? Cannot stringify null Node
by Igor JStarter
Igor JStarter [http://community.jboss.org/people/izgur] created the discussion
"can't call a .NET web service ? Cannot stringify null Node"
To view the discussion, visit: http://community.jboss.org/message/583614#583614
--------------------------------------------------------------
Hey!
I'm using Jboss5.1, ESB4.8 and Riftsaw2.1... and develop web services with BPEL.... using JBoss Web Services- native 3.2.1...
They couldn't help me on theRiftsaw forum : http://community.jboss.org/thread/161703 http://community.jboss.org/thread/161703
In this discussion i posted the wsdl I'm retrieving.
*PROBLEM:*
2011-01-27 09:36:20,503 ERROR [org.apache.ode.jacob.vpu.JacobVPU] (ODEServer-1) Method "onResponse" in class "org.apache.ode.bpel.runtime.INVOKE$2" threw an unexpected exception.
java.lang.IllegalArgumentException: Cannot stringify null Node!
I have already created TRACE logging for org.jboss.ws and org.jboss.wsf, but still I can't see what the problem could be. Everybody write that there must be a SoapAction not included error.... but I see that JBoss knows what the SoapAction is...
*LOG:*
2011-01-27 14:23:56,456 TRACE [org.jboss.ws.core.MessageTrace] (ODEServer-7) Outgoing Request Message
<env:Envelope xmlns:env=' http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/'>
<env:Header/>
<env:Body>
<SayHello xmlns=' http://tempuri.org/ http://tempuri.org/'>
<p:name xmlns:p=' http://tempuri.org/ http://tempuri.org/'>2</p:name>
</SayHello>
</env:Body>
</env:Envelope>
2011-01-27 14:23:56,517 TRACE [org.jboss.ws.core.CommonMessageContext] (ODEServer-7) get(org.jboss.ws.*DOMContentCanonicalNormalization*): null
2011-01-27 14:23:56,518 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) getChildNodes
2011-01-27 14:23:56,518 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) getChildNodes
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP] (ODEServer-7) Read input stream with metadata={X-AspNet-Version=[2.0.50727], Date=[Thu, 27 Jan 2011 13:35:47 GMT], Content-Length=[698], MicrosoftOfficeWebServer=[5.0_Pub], ResponseCodeMessage=Internal Server Error, ResponseCode=500, Content-Type=[text/xml; charset=utf-8], Connection=[close], X-Powered-By=[ASP.NET], Server=[Microsoft-IIS/6.0], Protocol=HTTP/1.1, Cache-Control=[private]}
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [X-AspNet-Version=2.0.50727]
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [Date=Thu, 27 Jan 2011 13:35:47 GMT]
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [Content-Length=698]
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [MicrosoftOfficeWebServer=5.0_Pub]
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [Content-Type=text/xml; charset=utf-8]
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [Connection=close]
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [X-Powered-By=ASP.NET]
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [Server=Microsoft-IIS/6.0]
2011-01-27 14:23:56,916 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) [Cache-Control=private]
2011-01-27 14:23:56,916 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) createMessage: [contentType=text/xml; charset=utf-8]
2011-01-27 14:23:56,917 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) createMessage
<s:Envelope xmlns:s=" http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a=" http://schemas.microsoft.com/ws/2005/05/addressing/none http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</faultcode><faultstring xml:lang="sl-SI">The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring></s:Fault></s:Body></s:Envelope>
2011-01-27 14:23:56,917 TRACE [org.jboss.ws.core.soap.MessageFactoryImpl] (ODEServer-7) Using style: document
2011-01-27 14:23:56,917 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-7) createElement { http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/}s:Envelope
2011-01-27 14:23:56,918 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-7) createElement { http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/}s:Body
2011-01-27 14:23:56,918 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-7) createElement { http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/}s:Fault
2011-01-27 14:23:56,919 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) getChildNodes
2011-01-27 14:23:56,919 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) -----------------------------------
2011-01-27 14:23:56,920 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) Transitioning from XML_VALID to DOM_VALID
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) removeContents
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) getChildElements
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) getChildNodes
2011-01-27 14:23:56,920 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-7) createElement {}faultcode
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPFaultImpl] (ODEServer-7) convertToFaultElement : org.jboss.ws.core.soap.SOAPFaultElementImpl@1be361d[[faultcode: null]]
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) addChildElement: org.jboss.ws.core.soap.SOAPFaultElementImpl@1be361d[[faultcode: null]]
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) appendChild: org.jboss.ws.core.soap.SOAPFaultElementImpl@1be361d[[faultcode: null]]
2011-01-27 14:23:56,920 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-7) createElement {}faultstring
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPFaultImpl] (ODEServer-7) convertToFaultElement : org.jboss.ws.core.soap.SOAPFaultElementImpl@d2c996[[faultstring: null]]
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) addChildElement: org.jboss.ws.core.soap.SOAPFaultElementImpl@d2c996[[faultstring: null]]
2011-01-27 14:23:56,920 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) appendChild: org.jboss.ws.core.soap.SOAPFaultElementImpl@d2c996[[faultstring: null]]
2011-01-27 14:23:56,921 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) -----------------------------------
2011-01-27 14:23:56,921 TRACE [org.jboss.ws.core.soap.SOAPContentElement] (ODEServer-7) getChildNodes
2011-01-27 14:23:56,921 TRACE [org.jboss.ws.core.MessageTrace] (ODEServer-7) Incoming Response Message
<s:Envelope xmlns:s=' http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/'>
<s:Body>
<s:Fault xmlns:s=' http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/'>
<faultcode xmlns:a=' http://schemas.microsoft.com/ws/2005/05/addressing/none http://schemas.microsoft.com/ws/2005/05/addressing/none'>a:ActionNotSupported</faultcode>
<faultstring xml:lang='sl-SI'>The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring>
</s:Fault>
</s:Body>
</s:Envelope>
Please help ...
Any idea what could solve the problem?
BR, Igor!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583614#583614]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JBoss AOP] - Error in deploying .aop file
by maze A
maze A [http://community.jboss.org/people/maazzzeeee] created the discussion
"Error in deploying .aop file"
To view the discussion, visit: http://community.jboss.org/message/583774#583774
--------------------------------------------------------------
*I have installed the "jbossesb-4.9" in jboss-5.1.0.GA application server. whenever I try to deploy my aop file (LoggingAspect.aop) in "jboss-5.1.0.GA/server/all/deploy" folder, this error pops up:*
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/home/maazzzeeee/Desktop/jboss-5.1.0.GA/server/all/deploy/LoggingAspect.aop/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=aop
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
*Do you have any idea?*
*I am dealing with this problem for more that a week. I really appreciate any suggestion.*
*
*
*Actually, I want to intercept "service actions" in the jbossesb services. before combining AS 5.1.0 and JbossESB-4.9, I tested it on the jboss-esb-server. But, in that configuration, I couldn't see any intereption.*
*This is my jboss-aop.xml file:*
<?xml version="1.0" encoding="UTF-8"?>
<!-- -->
<aop xmlns="urn:jboss:aop-beans:1.0">
<interceptor name="LoggingAspect" class="org.jboss.soa.esb.samples.quickstart.helloworld.LoggingAspect"/>
<bind pointcut="execution(* org.jboss.soa.esb.samples.quickstart.helloworld.MyJMSListenerAction->*(..))">
<interceptor-ref name="LoggingAspect"/>
</bind >
</aop>
*And this is my /interceptor java code:*
package org.jboss.soa.esb.samples.quickstart.helloworld;
import org.jboss.aop.advice.Interceptor;
import org.jboss.aop.joinpoint.Invocation;
import org.jboss.aop.joinpoint.ConstructorInvocation;
import org.jboss.aop.joinpoint.FieldWriteInvocation;
import org.jboss.aop.joinpoint.MethodInvocation;
public class LoggingAspect implements Interceptor
{
@Override
public String getName() {
return "LogInterceptor";
}
@Override
public Object invoke(Invocation invocation) throws Throwable {
long time=System.currentTimeMillis();
try {
return invocation.invokeNext();
} finally
{
time=System.currentTimeMillis()-time;
if (invocation instanceof MethodInvocation) {
MethodInvocation mi = (MethodInvocation) invocation;
String clazz="";
try
{
clazz=mi.getTargetObject().getClass().toString();
}
catch (Throwable e)
{
// TODO
}
}
}
}
}
*I also attached my aop file
*
*Thanks!
*
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583774#583774]
Start a new discussion in JBoss AOP at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JBoss Remoting] - Re: LeasePinger, sessionId, jboss messaging
by Mark Torres
Mark Torres [http://community.jboss.org/people/mark_v_torres] created the discussion
"Re: LeasePinger, sessionId, jboss messaging"
To view the discussion, visit: http://community.jboss.org/message/583131#583131
--------------------------------------------------------------
Hi Ron,
Thanks for your reply.
Its been a couple of weeks so the exact behavior is a little hazy in my memory. I'll try to test later.
For the case where the LeasePinger awakes first, what happens is the server cleans up its associated resources for that lease, but the client eventually still tries to use the lease.
We eventually end up with repeating log entries that contains the following
WARN [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ http://community.jboss.org/mailto:ControlMonitorTimerTask@2b22ebae ControlMonitorTimerTask@2b22ebae: detected failure on control connection Thread[control: Socket[addr=/*.*.*.*,port=*****,localport=*****],5,jboss] (3j011-cnnwn5-gg6xpq1c-1-gg6xw0ay-c: requesting new control connection
WARN [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ http://community.jboss.org/mailto:ControlMonitorTimerTask@2b22ebae ControlMonitorTimerTask@2b22ebae: detected failure on control connection Thread[control: Socket[addr=/*.*.*.*,port=*****,localport=*****],5,jboss] (3j011-cnnwn5-gg6xpq1c-1-gg6xw0ay-c: requesting new control connection
WARN [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ http://community.jboss.org/mailto:ControlMonitorTimerTask@2b22ebae ControlMonitorTimerTask@2b22ebae: detected failure on control connection Thread[control: Socket[addr=/*.*.*.*,port=*****,localport=*****],5,jboss] (3j011-cnnwn5-gg6xpq1c-1-gg6xw0ay-c: requesting new control connection
WARN [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ http://community.jboss.org/mailto:ControlMonitorTimerTask@2b22ebae ControlMonitorTimerTask@2b22ebae: detected failure on control connection Thread[control: Socket[addr=/*.*.*.*,port=*****,localport=*****],5,jboss] (3j011-cnnwn5-gg6xpq1c-1-gg6xw0ay-c: requesting new control connection
+But I'm not sure your "recreation" is a faithful representation of the problem. When you say "the connection becomes dead on the server side", do you mean+
Neither the server nor the client gets restarted. They remain connected on the network, but on my "recreation" the client experienced a heavy load that its not able to send out pings for some time.
"The connection becomes dead on the server side" - What I mean to say is that the resources have been cleaned up from the server side for that lease, but the actual server jvm is still running.
Here's the trace log that I got from the server during an unsuccesful disconnection...
--connect
2010-12-28 09:15:09,940 TRACE [org.jboss.remoting.transport.socket.ServerThread] blocking to read version from input stream
2010-12-28 09:15:19,911 TRACE [org.jboss.remoting.transport.socket.ServerThread] read version 22 from input stream
2010-12-28 09:15:19,911 TRACE [org.jboss.remoting.transport.socket.ServerThread] blocking to read invocation from unmarshaller
2010-12-28 09:15:19,911 TRACE [org.jboss.remoting.transport.socket.ServerThread] read InvocationRequest[5d4a62, $PING$] from unmarshaller
2010-12-28 09:15:19,911 TRACE [org.jboss.remoting.transport.socket.ServerThread] about to call SocketServerInvoker[192.168.1.3:4457].invoke()
2010-12-28 09:15:19,911 TRACE [org.jboss.remoting.ServerInvoker] SocketServerInvoker[192.168.1.3:4457] received $PING$
2010-12-28 09:15:19,911 TRACE [org.jboss.remoting.ServerInvoker] Getting lease for invoker session id: 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.ServerInvoker] Lease[406c7e:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] matches: leasePingerId: 5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.Lease] Lease[406c7e:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] requestMap: {ClientHolderKey={5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6=org.jboss.remoting.ClientHolder@be8e12}, timeStamp=1293545641187, leasePingerId=5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9}
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.Lease] Lease[406c7e:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] last update: 1293545631187, this update: 1293545641187
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.Lease] Lease[406c7e:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] updating: new Client list:
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.Lease] 5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9: 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.ServerInvoker] Updated lease for invoker session id (5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8)
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.ServerInvoker] SocketServerInvoker[192.168.1.3:4457] returning InvocationResponse[6159c4, true]
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.transport.socket.ServerThread] SocketServerInvoker[192.168.1.3:4457].invoke() returned InvocationResponse[6159c4, true]
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.transport.socket.ServerThread] creating response instance
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.transport.socket.ServerThread] wrote response to the output stream
2010-12-28 09:15:19,912 TRACE [org.jboss.remoting.transport.socket.ServerThread] preparing to process next invocation invocation
-- disconnect
2010-12-28 09:15:59,806 TRACE [org.jboss.remoting.Lease] Lease[406c7e:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] did not receive ping: 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8
2010-12-28 09:15:59,808 TRACE [org.jboss.remoting.Lease] Lease[406c7e:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] notifying listeners about 1 expired client(s)
2010-12-28 09:15:59,808 DEBUG [org.jboss.remoting.ConnectionNotifier] mailto:org.jboss.remoting.ConnectionNotifier@fe8c4 org.jboss.remoting.ConnectionNotifier@fe8c4 Server connection lost to client (session id = 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.ServerInvoker] SocketServerInvoker[192.168.1.3:4457] removing server callback handler ServerInvokerCallbackHandler[5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6+5c4o16-3bs5xt-gi8uuno8-1-gi8uw25b-d].
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.Client] Client[4806599:3j011-y3aa1o-gi84ufr8-1-gi8uxqvf-c] entering disconnect()
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.MicroRemoteClientInvoker] SocketClientInvoker[43fb68, bisocket://192.168.1.6:452753942] entering terminateLease() for null
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.MicroRemoteClientInvoker] SocketClientInvoker[43fb68, bisocket://192.168.1.6:452753942] leasePinger is null: must have been shut down already
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.MicroRemoteClientInvoker] SocketClientInvoker[43fb68, bisocket://192.168.1.6:452753942] leaving terminateLease() for null
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.InvokerRegistry] destroying client invoker InvokerLocator [bisocket://192.168.1.6:452753942/callback?callbackServerHost=192.168.1.6&callbackServerPort=452753942&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=5c4o16-3bs5xt-gi8uuno8-1-gi8uw24g-c&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper], config {callbackErrorsAllowed=1, registerCallbackListener=false, callbackServerProtocol=bisocket, serverInvokerCallbackHandler=ServerInvokerCallbackHandler[5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6+5c4o16-3bs5xt-gi8uuno8-1-gi8uw25b-d], stopLeaseOnFailure=true, socket.check_connection=false, listenerId=5c4o16-3bs5xt-gi8uuno8-1-gi8uw25b-d, unmarshaller=org.jboss.jms.wireformat.JMSWireFormat, marshaller=org.jboss.jms.wireformat.JMSWireFormat, serverInvoker=SocketServerInvoker[192.168.1.3:4457], clientLeasePeriod=10000, onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool, useClientConnectionIdentity=true, callbackServerHost=192.168.1.6, JBM_clientMaxPoolSize=200, callbackTimeout=10000, clientMaxPoolSize=1, validatorPingTimeout=5000, isCallbackServer=true, validatorPingPeriod=10000, numberOfRetries=10, serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper, failureDisconnectTimeout=0, clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper, callbackServerPort=452753942, guid=5c4o16-3bs5xt-gi8uuno8-1-gi8uw24g-c, dataType=jms, serverBindPort=4457, datatype=jms, serverBindAddress=192.168.1.3, timeout=10000}
2010-12-28 09:15:59,809 DEBUG [org.jboss.remoting.InvokerRegistry] removed SocketClientInvoker[43fb68, bisocket://192.168.1.6:452753942] from registry
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.InvokerRegistry] disconnecting SocketClientInvoker[43fb68, bisocket://192.168.1.6:452753942]
2010-12-28 09:15:59,809 DEBUG [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] SocketClientInvoker[43fb68, bisocket://192.168.1.6:452753942] disconnecting ...
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.MicroRemoteClientInvoker] SocketClientInvoker[43fb68, bisocket://192.168.1.6:452753942] disconnecting ...
2010-12-28 09:15:59,809 TRACE [org.jboss.remoting.MicroRemoteClientInvoker] SocketClientInvoker[43fb68, bisocket://192.168.1.6:452753942] disconnected
2010-12-28 09:15:59,809 DEBUG [org.jboss.remoting.Client] Client[4806599:3j011-y3aa1o-gi84ufr8-1-gi8uxqvf-c] is disconnected
2010-12-28 09:15:59,809 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] ServerInvokerCallbackHandler[5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6+5c4o16-3bs5xt-gi8uuno8-1-gi8uw25b-d] shut down
2010-12-28 09:15:59,810 DEBUG [org.jboss.remoting.ConnectionNotifier] mailto:org.jboss.remoting.ConnectionNotifier@fe8c4 org.jboss.remoting.ConnectionNotifier@fe8c4 notified ConnectionManager[1aea727] of connection lost to: 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6
2010-12-28 09:15:59,810 TRACE [org.jboss.remoting.Lease] Lease[406c7e:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] Notified connection listener of lease expired due to lost connection from client (client session id = 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6
2010-12-28 09:15:59,810 TRACE [org.jboss.remoting.Lease] Lease[406c7e:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] removed lease:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8
--ping returns true but should be false
2010-12-28 09:18:47,448 TRACE [org.jboss.remoting.transport.socket.ServerThread] read version 22 from input stream
2010-12-28 09:18:47,448 TRACE [org.jboss.remoting.transport.socket.ServerThread] blocking to read invocation from unmarshaller
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.transport.socket.ServerThread] read InvocationRequest[1887dd5, $PING$] from unmarshaller
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.transport.socket.ServerThread] about to call SocketServerInvoker[192.168.1.3:4457].invoke()
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.ServerInvoker] SocketServerInvoker[192.168.1.3:4457] received $PING$
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.ServerInvoker] Getting lease for invoker session id: 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.Lease] Lease[c83cfd:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] initialized with lastUpdate: 1293545848717
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.Lease] Lease[c83cfd:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9] initialized with requestPayload: {5c4o16-3bs5xt-gi8uuno8-1-gi8uw21m-6=org.jboss.remoting.ClientHolder@1c232a}
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.Lease] leasePingerId: 5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.Lease] Starting lease for client invoker (session id = 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8) with lease window time of 20000
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.ServerInvoker] No lease established for invoker session id (5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8), so starting a new one:Lease[c83cfd:5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8:5c4o16-3bs5xt-gi8uuno8-1-gi8uw222-9]
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.ServerInvoker] SocketServerInvoker[192.168.1.3:4457] returning InvocationResponse[148ccb8, true]
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.transport.socket.ServerThread] SocketServerInvoker[192.168.1.3:4457].invoke() returned InvocationResponse[148ccb8, true]
2010-12-28 09:18:47,449 TRACE [org.jboss.remoting.transport.socket.ServerThread] creating response instance
2010-12-28 09:18:47,450 TRACE [org.jboss.remoting.transport.socket.ServerThread] wrote response to the output stream
2010-12-28 09:18:47,450 TRACE [org.jboss.remoting.transport.socket.ServerThread] preparing to process next invocation invocation
2010-12-28 09:18:47,450 TRACE [org.jboss.remoting.transport.socket.ServerThread] blocking to read version from input stream
2010-12-28 09:18:47,486 TRACE [org.jboss.remoting.transport.socket.ServerThread] read version 22 from input stream
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.transport.socket.ServerThread] blocking to read invocation from unmarshaller
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.transport.socket.ServerThread] read InvocationRequest[d1e832, self, $PING$] from unmarshaller
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.transport.socket.ServerThread] about to call SocketServerInvoker[192.168.1.3:4457].invoke()
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.ServerInvoker] SocketServerInvoker[192.168.1.3:4457] received $PING$
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.ServerInvoker] Checking lease for invoker session id: 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.ServerInvoker] Found lease for invoker session id (5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8)
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.ServerInvoker] SocketServerInvoker[192.168.1.3:4457] responding true to $PING$ for invoker sessionId 5c4o16-3bs5xt-gi8uuno8-1-gi8uw21q-8
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.transport.socket.ServerThread] SocketServerInvoker[192.168.1.3:4457].invoke() returned true
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.transport.socket.ServerThread] creating response instance
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.transport.socket.ServerThread] wrote response to the output stream
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.transport.socket.ServerThread] preparing to process next invocation invocation
2010-12-28 09:18:47,487 TRACE [org.jboss.remoting.transport.socket.ServerThread] blocking to read version from input stream
2010-12-28 09:18:57,440 TRACE [org.jboss.remoting.transport.socket.ServerThread] read version 22 from input stream
2010-12-28 09:18:57,440 TRACE [org.jboss.remoting.transport.socket.ServerThread] blocking to read invocation from unmarshaller
2010-12-28 09:18:57,440 TRACE [org.jboss.remoting.transport.socket.ServerThread] read InvocationRequest[84a74, InternalI
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583131#583131]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[jBPM] - some jBPM5 - Oryx integration questions
by vsp
vsp [http://community.jboss.org/people/vsp] created the discussion
"some jBPM5 - Oryx integration questions"
To view the discussion, visit: http://community.jboss.org/message/582462#582462
--------------------------------------------------------------
Hi,
Given that Oryx is not distributed with jBPM5, I was wondering what work was done on Oryx in order to integrate it with jBPM5. In particular, how are the models persisted: in Oryx's db schema in JSON format? in jBPM5's schema in BPMN 2.0 format? both? If one modifies an existing model through Oryx, do the changes get reflected in the corresponding BPMN model?
I noticed the jbpm-installer uses a version 1.0.0.26 - does this correspond with Intalio's version? If so, could the latest Intalio version (1.0.0.59 or so) be used instead of 1.0.0.26? How different are these distributions from the original Oryx from google code?
Also, is this integration work different than what Signavio did to integrate with jBPM4?
Many questions - just trying to clarify the landscape :)
Thanks,
Vlad
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/582462#582462]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JNDI and Naming] - Re: javax.naming.NameNotFoundException: persistence not bound
by rac tech
rac-tech [http://community.jboss.org/people/rac-tech] created the discussion
"Re: javax.naming.NameNotFoundException: persistence not bound"
To view the discussion, visit: http://community.jboss.org/message/577084#577084
--------------------------------------------------------------
Thank you for the reply
The JBoss version is 5.1.0.
Persistent unit(smalllake-bopc) is deployed with a warning just after this exception is thrown. Please see a portion of the log below
----------------------------------------------------------------------------------------------------------
Caused by: javax.naming.NameNotFoundException: persistence not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
....
....
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1400)
... 133 more
09:10:29,332 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=sss.ear/sss.jar#smalllake-bopc
09:10:29,379 INFO [Version] Hibernate Annotations 3.4.0.GA
09:10:29,394 INFO [Environment] Hibernate 3.3.1.GA
09:10:29,394 INFO [Environment] hibernate.properties not found
09:10:29,394 INFO [Environment] Bytecode provider name : javassist
09:10:29,394 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling
09:10:29,457 INFO [Version] Hibernate Commons Annotations 3.1.0.GA
09:10:29,457 INFO [Version] Hibernate EntityManager 3.4.0.GA
09:10:29,488 INFO [Ejb3Configuration] Processing PersistenceUnitInfo [
name: smalllake-bopc
...]
09:10:29,582 WARN [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/577084#577084]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[jBPM] - FileSystemRootDirectory breaks dev & deployment use-cas
by keith freeman
keith freeman [http://community.jboss.org/people/8forty] created the discussion
"FileSystemRootDirectory breaks dev & deployment use-cas"
To view the discussion, visit: http://community.jboss.org/message/583731#583731
--------------------------------------------------------------
Hello,
I just started using JBPM 4.3 with JBoss 5.1, and ran into a problem with the FileSystemRootDirectory parameter in the jbpmeditor web.xml. In development my team has always been able to use jboss installed locally (to our /home/<user-id> directories) and just copy around changes with no problems. Now that we've installed and are trying to use the jbpmeditor, this (well-known I think) ability to just copy the jboss directory tree around and use is broken because of the hard-coded path in FileSystemRootDirectory which (in our case) is different on every machine.
Simply using a directory that's consistent across all our dev and test machines isn't practical for us (we've been doing it this way for 3 years). Is there any workaround, e.g. can I use directory relative to an environment variable?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583731#583731]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JBoss Tools] - Forging of the Forge Tools
by Koen Aers
Koen Aers [http://community.jboss.org/people/koen.aers%40jboss.com] modified the blog post:
"Forging of the Forge Tools"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/01/27/forging-of-the...
--------------------------------------------------------------
Over the past few weeks, I have started the integration of http://seamframework.org/Documentation/SeamForge Seam Forge into http://www.jboss.org/tools JBoss Tools. Today I am happy to present the first results of this work.
h1. Installation
If you are familiar with the Eclipse platform the installation should be a breeze for you. The easiest way is to http://www.eclipse.org/downloads/ download a recent Eclipse version and use the 'Help->Install New Software...' wizard to install the latest and greatest JBoss Tools from the http://download.jboss.org/jbosstools/updates/development/ update site. Don't forget to include the Maven integration for Eclipse as we will need it later on. After this, use the same mechanism to install the forge tools from http://download.jboss.org/jbosstools/extras/forge-tools.zip this update archive. Restart Eclipse and you should be set to go.
http://community.jboss.org/servlet/JiveServlet/showImage/38-3555-11210/In... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-3555-1121...
h1. Starting and Stopping
Now that the installation is dealt with, let's have a look whether everything went ok. You can bring up the "Forge Console View" by selecting 'Window->Show View->Other...' and then 'Seam Forge->Forge Console'.
http://community.jboss.org/servlet/JiveServlet/showImage/38-3555-11212/Fo... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-3555-1121... As you can see the Forge Console View has a toolbar and a dropdown menu that allow you to start and stop Forge. The initial message pane indicates that Forge is not running. Let's get going and push the 'Start Forge' button.
http://community.jboss.org/servlet/JiveServlet/showImage/38-3555-11213/Fo... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-3555-1121...
After a while, the Forge welcome banner appears and you are invited to enter forge commands. The very convenient tab completion suggesting the list or possible commands does not work yet, but you can get the suggestions anyway by pressing tab followed by a return. Also, the coloring is not yet enabled like when using Forge directly in a terminal window. When you're done working you can stop Forge by pushing the 'Stop Forge' button.
h1. Create a Project
To make things a bit more interesting, let's try the tutorial from http://community.jboss.org/people/lincolnthree/blog/2010/12/31/forge-100a... Lincoln's blog. We create a new project called 'foo' with top level package 'org.foo':
[no project] workspace $ new-project --named foo --topLevelPackage org.foo
http://community.jboss.org/servlet/JiveServlet/showImage/38-3555-11214/Fo... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-3555-1121... Now the project is created but unfortunately, we cannot see it in our workspace. This is one of the obvious features that need to be added. For now, we have to import the project in the workspace. Here is where the Maven plugins come into play. For Forge projects are indeed Maven projects too. Select 'File->Import...' and then 'Maven->Existing Maven Project'. Point the wizard at the workspace root and the 'foo' project should show up in the list of projects to import. After importing the project shows up in the package explorer.
http://community.jboss.org/servlet/JiveServlet/showImage/38-3555-11215/Pa... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-3555-1121... We enter the next few commands from the tutorial:
[foo] foo $ install forge.scaffold
[foo] foo $ new-entity --named Person
[foo] Person.java $ new-field string --fieldName firstName
[foo] Person.java $ new-field string --fieldName lastName
[foo] Person.java $ cd ..
[foo] domain $ scaffold generate-metawidget-jsf *.java
To see which changes are performed in the project by these commands we need to refresh the project.
http://community.jboss.org/servlet/JiveServlet/showImage/38-3555-11216/Co... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-3555-1121...
Again, it would be good if after issuing each command the relevant changes would be highlighted by setting the relevant folder, file or file element selected. This is more work for the future.
h1. The Future
As suggested, a lot more work is waiting... Some of the features that are on the list are:
* Adding a preference page to be able to add and select Forge runtimes.
* Support for tab completion suggesting the list of possible commands.
* Support for command history.
* Support for colors in the Eclipse Forge Console.
* Show appropriate feedback after each command.
* etc.
If you are interested in helping out implementing some of these features or if you just want to view the code implementing the current console, you can find the sources in the https://anonsvn.jboss.org/repos/jbosstools/trunk/forge/ JBoss Tools SVN.
Happy forging!
Koen
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/01/27/forging-of-the...]
13 years, 5 months
