[JBoss JIRA] Created: (JBESB-459) Create a message validation cartridge that can be used by Smooks to perform message validation.
by Tom Fennelly (JIRA)
Create a message validation cartridge that can be used by Smooks to perform message validation.
-----------------------------------------------------------------------------------------------
Key: JBESB-459
URL: http://jira.jboss.com/jira/browse/JBESB-459
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Mark Little
Priority: Optional
Fix For: 4.2
Something as simple as cartridge that would allow you target and apply regexp and XPath expressions at parts of a message, generating error/warning reports. I actually used Smooks to prototyped something that's conceptually similar from a validation perspective - analyze a website using Smooks, and generate a report contain possible browser issues with each page (message) e.g. on browser "X" on Mac Os X, this part of the markup may cause usability issues etc (http://milyn.codehaus.org/Smooks+Report+Generator).
The cartridge could allow you create "validation" resources that can be targeted at message exchanges (fragments, elements, attributes etc). This might support applying regexp expressions to data values (match, not-match etc - easy enough) as well as using xpath (has-child-element etc easy enough too *I think*). Would obviously get more difficult if you started to add some form of expression language to it - "if attribute matches X and doesn't have child element Y" etc.
Might be possible to use JBoss Rules and some form of DSL to wrap the xpath stuff (or even the regex stuff too).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBESB-1516) Quickstart that demonstrates Smooks JMSRouter
by Daniel Bevenius (JIRA)
Quickstart that demonstrates Smooks JMSRouter
----------------------------------------------
Key: JBESB-1516
URL: http://jira.jboss.com/jira/browse/JBESB-1516
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation, Examples
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.3
This quickstart will show how one can utilize Smooks JMSRouter to route transformed message fragments to a JMS destination.
The advantage of this is that instead of transforming the whole document and then routing, one can have Smooks route the fragment to a destination directly after the transformation has been performed. Combining this with Smooks support for SAX parsing should also result in a smaller memory footprint (no need to parse a the whole document).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBESB-692) WARN [BisocketClientInvoker] Message when using bootstrapper
by Burr Sutter (JIRA)
WARN [BisocketClientInvoker] Message when using bootstrapper
------------------------------------------------------------
Key: JBESB-692
URL: http://jira.jboss.com/jira/browse/JBESB-692
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 2
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Minor
Fix For: 4.2
The following warning & stack trace show up on the AS console whenever you "Ctrl-C" the bootstrapper.
15:31:36,109 WARN [BisocketClientInvoker] Unable to send ping: shutting down Pi
ngTimerTask
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:115)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimer
Task.run(BisocketClientInvoker.java:497)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
To recreate:
quickstart helloworld
'ant deploy-jms-dests'
'ant run'
Ctrl-C
The message pops up on the console.
Either we need to fix whatever is in the bootstrapper that JBoss Messaging doesn't like (disconnection must be improper) or we need to turn off this warning level. Additional warnings sometimes appear as well:
15:34:53,593 WARN [SimpleConnectionManager] ConnectionManager[c2b246] cannot lo
ok up remoting session ID 5c4o22-n5wjzb-f44hz8li-1-f44hz8ze-4
15:34:53,593 WARN [SimpleConnectionManager] A problem has been detected with th
e connection to remote client 5c4o22-n5wjzb-f44hz8li-1-f44hz8ze-4. It is possibl
e the client has exited without closing its connection(s) or there is a network
problem. All connection resources corresponding to that client process will now
be removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBESB-569) JBoss ESB Template Enhancements
by Tom Cunningham (JIRA)
JBoss ESB Template Enhancements
-------------------------------
Key: JBESB-569
URL: http://jira.jboss.com/jira/browse/JBESB-569
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.2 Milestone Release 2
Reporter: Tom Cunningham
Assigned To: Tom Cunningham
Here's a list of enhancements that have been suggested:
Parameterize the name of the project in the build.xml to match the eclipse project name
Parameterize the classnames of the ESB code we generate
Add directory jars (jaxr,scout,juddi)
To conserve space, pare down jboss-all jar into just the jms classes we need
Use InitialContext in SendJMSMessage.java (we have a jndi.properties file)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBESB-1145) ESB server startup : java.lang.ClassCircularityError: EDU/oswego/cs/dl/util/concurrent/LinkedQueue
by Tom Cunningham (JIRA)
ESB server startup : java.lang.ClassCircularityError: EDU/oswego/cs/dl/util/concurrent/LinkedQueue
--------------------------------------------------------------------------------------------------
Key: JBESB-1145
URL: http://jira.jboss.com/jira/browse/JBESB-1145
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1 IR1
Reporter: Tom Cunningham
Assigned To: Mark Little
Fix For: 4.2.1
I've seen this a couple of times now - occurs every once in a while during startup of a completely clean ESB server :
15:55:09,952 INFO [JBoss4ESBDeployer] create esb service, jbpm.esb
15:55:09,985 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=JbpmDS' to JNDI name 'java:JbpmDS'
15:55:10,006 INFO [TomcatDeployer] deploy, ctxPath=/jbpm-console, warUrl=.../tmp/deploy/tmp7718jbpm-console-exp.war/
15:55:10,122 INFO [ContextConfig] WARNING: Security role name user used in an <auth-constraint> without being defined in a <security-role>
15:55:10,544 WARN [AbstractThreadedManagedLifecycle] Unexpected error from doRun()
java.lang.ClassCircularityError: EDU/oswego/cs/dl/util/concurrent/LinkedQueue
at org.jboss.jms.client.state.SessionState.<init>(SessionState.java:137)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateSessionDelegate(StateCreationAspect.java:137)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect2.invoke(StateCreationAspect2.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.ConnectionAspect.handleCreateSessionDelegate(ConnectionAspect.java:161)
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.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.createSessionDelegate(ClientConnectionDelegate.java)
at org.jboss.jms.client.JBossConnection.createSessionInternal(JBossConnection.java:269)
at org.jboss.jms.client.JBossConnection.createQueueSession(JBossConnection.java:165)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.addAnotherSession(JmsConnectionPool.java:142)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:183)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getQueueSession(JmsConnectionPool.java:206)
at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:144)
at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:520)
at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:436)
at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:380)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:223)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:205)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:268)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:252)
at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
at java.lang.Thread.run(Thread.java:613)
15:55:10,545 WARN [AbstractThreadedManagedLifecycle] Unexpected error from doRun()
java.lang.ClassCircularityError: EDU/oswego/cs/dl/util/concurrent/LinkedQueue
at org.jboss.jms.client.state.SessionState.<init>(SessionState.java:137)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateSessionDelegate(StateCreationAspect.java:137)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect2.invoke(StateCreationAspect2.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.ConnectionAspect.handleCreateSessionDelegate(ConnectionAspect.java:161)
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.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.createSessionDelegate(ClientConnectionDelegate.java)
at org.jboss.jms.client.JBossConnection.createSessionInternal(JBossConnection.java:269)
at org.jboss.jms.client.JBossConnection.createQueueSession(JBossConnection.java:165)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.addAnotherSession(JmsConnectionPool.java:142)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:183)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getQueueSession(JmsConnectionPool.java:206)
at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:144)
at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:520)
at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:436)
at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:380)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:223)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:205)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:268)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:252)
at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
at java.lang.Thread.run(Thread.java:613)
15:55:10,547 WARN [AbstractThreadedManagedLifecycle] Unexpected error from doRun()
java.lang.ClassCircularityError: EDU/oswego/cs/dl/util/concurrent/LinkedQueue
at org.jboss.jms.client.state.SessionState.<init>(SessionState.java:137)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateSessionDelegate(StateCreationAspect.java:137)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect2.invoke(StateCreationAspect2.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.ConnectionAspect.handleCreateSessionDelegate(ConnectionAspect.java:161)
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.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$createSessionDelegate_6052335267724906805.invokeNext(ClientConnectionDelegate$createSessionDelegate_6052335267724906805.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.createSessionDelegate(ClientConnectionDelegate.java)
at org.jboss.jms.client.JBossConnection.createSessionInternal(JBossConnection.java:269)
at org.jboss.jms.client.JBossConnection.createQueueSession(JBossConnection.java:165)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.addAnotherSession(JmsConnectionPool.java:142)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:183)
at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getQueueSession(JmsConnectionPool.java:206)
at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:144)
at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:520)
at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:436)
at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:380)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:223)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:205)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:268)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:252)
at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBESB-1362) Place all ESB deployments inside it's own directory deploy/esb
by jarkko Lietolahti (JIRA)
Place all ESB deployments inside it's own directory deploy/esb
--------------------------------------------------------------
Key: JBESB-1362
URL: http://jira.jboss.com/jira/browse/JBESB-1362
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1
Reporter: jarkko Lietolahti
To make the deployment more clear place all ESB related deployments inside it's own directory.
Currently everything (core, services, samples) deploy directory to server/default/deploy directory and mixes with everything else there. JBoss AS supports "nested" deployments by default so instead of deploying to deploy -directory deploy to deploy/esb directory.
A (partial ?) list of affected deployments:
file:///home/jarkko/123/jboss-4.2.2.GA/server/default/deploy/jbossesb.esb
file:///home/jarkko/123/jboss-4.2.2.GA/server/default/deploy/jbossesb.sar
file:///home/jarkko/123/jboss-4.2.2.GA/server/default/deploy/jbpm.esb
file:///home/jarkko/123/jboss-4.2.2.GA/server/default/deploy/jbrules.esb
file:///home/jarkko/123/jboss-4.2.2.GA/server/default/deploy/smooks.esb
file:///home/jarkko/123/jboss-4.2.2.GA/server/default/deploy/soap.esb
file:///home/jarkko/123/jboss-4.2.2.GA/server/default/deploy/spring.esb
Also deploy samples to deploy/esb/samples
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBESB-1360) ServiceInvoker.deliverSync hangs
by Jiri Pechanec (JIRA)
ServiceInvoker.deliverSync hangs
--------------------------------
Key: JBESB-1360
URL: http://jira.jboss.com/jira/browse/JBESB-1360
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta, Web Services
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Priority: Critical
Attachments: test.log
Sometimes deliverSync blocks indefinitely. If the calling thread is terminated then it prints
WARN [Thread-1][CourierFactory] Calling cleanup on existing couriers for identity ID-DEFAULT and hangs !!
The last lines in log are
2007-11-22 12:03:10,776 DEBUG [Thread-1][org.jboss.soa.esb.lifecycle.LifecycleResource] Cleaning up resource using factory: org.jboss.soa.esb.couriers.CourierFactory$LifecycleCourierFactory@16cd83d8 with identity ID-DEFAULT
2007-11-22 12:03:10,776 WARN [Thread-1][org.jboss.soa.esb.couriers.CourierFactory] Calling cleanup on existing couriers for identity ID-DEFAULT
2007-11-22 12:03:10,784 DEBUG [Thread-1][org.jboss.soa.esb.couriers.CourierFactory] Courier allocation stacktrace
java.lang.Exception: Courier Assignment stacktrace
at org.jboss.soa.esb.couriers.CourierFactory.registerCourier(CourierFactory.java:148)
at org.jboss.soa.esb.couriers.CourierFactory.getCourier(CourierFactory.java:134)
at org.jboss.soa.esb.couriers.CourierFactory.getMessageCourier(CourierFactory.java:96)
at org.jboss.soa.esb.client.ServiceInvoker.getCourier(ServiceInvoker.java:338)
at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:404)
at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:370)
at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:259)
at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:155)
at org.jboss.soa.esb.samples.quickstart.webservice_consumer1.WebServiceConsumerTest.postESBMessage(WebServiceConsumerTest.java:60)
at org.jboss.soa.esb.samples.quickstart.webservice_consumer1.WebServiceConsumerTest.testWSConsumer(WebServiceConsumerTest.java:71)
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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604)
at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:36)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
The whole log is attached
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years