[JBoss JIRA] Created: (JBESB-2842) webservice_consumer1 error on deployment
by Neil Wallace (JIRA)
webservice_consumer1 error on deployment
----------------------------------------
Key: JBESB-2842
URL: https://jira.jboss.org/jira/browse/JBESB-2842
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.4 CP2
Reporter: Neil Wallace
Priority: Minor
Fix For: 4.4 CP3
webservice_consumer1 threw this error in the server log when running ant deploy
2009-09-16 10:29:00,745 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner
] Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@8ce1d89e { url=file:/home/nwallace/jboss-soa
-p.4.3.0/jboss-as/server/production/deploy/Quickstart_webservice_consumer1.esb }
deployer: org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer@feb215
status: Deployment FAILED reason: Could not create deployment: file:/home/nwal
lace/jboss-soa-p.4.3.0/jboss-as/server/production/tmp/deploy/tmp14613Quickstart_
webservice_consumer1.esb-contents/Quickstart_webservice_consumer1.war; - nested
throwable: (java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootst
rap classloader, but this RI (from jar:file:/home/nwallace/jboss-soa-p.4.3.0/jbo
ss-as/server/production/tmp/deploy/tmp14529jaxb-impl.jar!/com/sun/xml/bind/v2/mo
del/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism
to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2
se/1.5.0/docs/guide/standards/))
state: FAILED
watch: file:/home/nwallace/jboss-soa-p.4.3.0/jboss-as/server/production/deploy
/Quickstart_webservice_consumer1.esb
altDD: null
lastDeployed: 1253093321232
lastModified: 1253093321000
mbeans:
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBESB-2844) WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package
by Kevin Conner (JIRA)
WebService invocation is sometimes handled by CoyoteInvoker belonging to undeployed package
-------------------------------------------------------------------------------------------
Key: JBESB-2844
URL: https://jira.jboss.org/jira/browse/JBESB-2844
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.2.1, 4.4 CP3
Reporter: Jiri Pechanec
Assignee: Tom Fennelly
Priority: Minor
Fix For: 4.2.1 CP4
There were multiple packages deployed/undeployed in the test. The deployment of Quickstart_webservice_mtom.esb is started on line 413471. This package starts coyote invoker with hashCode 17a4c54 at the line 413681. The undeploymetn of this package starts on line 414408. The CoyoteInvoker with the given hashCode is stopped at line 414457.
The Quickstart_webservice_wsa.esb package deployment starts at line 414599.
The CoyotInvoker with hashCode d93db8 is started at line 414806.
Then the test message is sent via HTTP/SOAP and this request fails on line 515535 because it was served by the CoyoteInvoker with hashCode 17a4c54 so the one that belongs to previously undeployed package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBESB-2840) bpm_orchestration2 quickstart Extra Credit.
by Neil Wallace (JIRA)
bpm_orchestration2 quickstart Extra Credit.
--------------------------------------------
Key: JBESB-2840
URL: https://jira.jboss.org/jira/browse/JBESB-2840
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.4 CP2
Reporter: Neil Wallace
Priority: Minor
Fix For: 4.4 CP3
In the extra credit section, after a call of ant refreshProcess, the ant startProcess gives this error.
startProcess:
[echo] Sends a message to start the process instance
[java] Exception in thread "main" javax.naming.NameNotFoundException: quickstart_bpm_orchestration2_start_Request_gw not bound
[java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:581)
[java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:589)
[java] at org.jnp.server.NamingServer.getObject(NamingServer.java:595)
[java] at org.jnp.server.NamingServer.lookup(NamingServer.java:342)
[java] at org.jnp.server.NamingServer.lookup(NamingServer.java:316)
[java] at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
[java] at sun.rmi.transport.Transport$1.run(Transport.java:159)
[java] at java.security.AccessController.doPrivileged(Native Method)
[java] at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
[java] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
[java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
[java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
[java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
[java] at java.lang.Thread.run(Thread.java:619)
[java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
[java] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
[java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
[java] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:392)
[java] at org.jboss.soa.esb.samples.quickstarts.bpm_orchestration2.test.SendJMSMessageStart.setupConnection(SendJMSMessageStart.java:55)
[java] at org.jboss.soa.esb.samples.quickstarts.bpm_orchestration2.test.SendJMSMessageStart.main(SendJMSMessageStart.java:80)
BUILD FAILED
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBESB-2839) Can't load updated transformation in transform_XML2XML_simple quickstart
by Neil Wallace (JIRA)
Can't load updated transformation in transform_XML2XML_simple quickstart
------------------------------------------------------------------------
Key: JBESB-2839
URL: https://jira.jboss.org/jira/browse/JBESB-2839
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.4 CP2
Reporter: Neil Wallace
Priority: Minor
Fix For: 4.4 CP3
When trying out the next step in this quickstart, the command ant notifyUpdate, I get the following.
notifyUpdate:
[echo] Sending transformation update notification for transform "simple-transform" to deployed ESB.
[java] Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/soa/esb/testutils/JMSUtil
BUILD FAILED
/home/nwallace/jboss-soa-p.4.3.0/jboss-as/samples/quickstarts/transform_XML2XML_simple/build.xml:22: Java returned: 1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBESB-2329) FTP Gateway: error-delete does not work
by Thomas Guenter (JIRA)
FTP Gateway: error-delete does not work
---------------------------------------
Key: JBESB-2329
URL: https://jira.jboss.org/jira/browse/JBESB-2329
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Adapters
Affects Versions: 4.4
Environment: jbossesb-server-4.4.GA on Mac OS 10.5
Reporter: Thomas Guenter
Priority: Minor
If the error-delete attribute in a ftp-message-filter is set to "true" (as default), it is expected that no error file will be generated at all. Instead an error file with the default error-suffix is created in the (input-)directory.
Since the logic that handles these issues is implemented in the class org.jboss.soa.esb.listeners.gateway.AbstractFileGateway, it is likely that the FileGatewayListener is also affected but this hasn't been tested yet.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBESB-2836) Just a few little things in the ant help-quickstarts file.
by Neil Wallace (JIRA)
Just a few little things in the ant help-quickstarts file.
----------------------------------------------------------
Key: JBESB-2836
URL: https://jira.jboss.org/jira/browse/JBESB-2836
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.4 CP2
Reporter: Neil Wallace
Assignee: Kevin Conner
Priority: Minor
Fix For: 4.4 CP3
In the text from a call of ant help-quickstarts.
1. There's a ref to section 2.2 of the Getting started doc to do with different jndi settings but that section doesn't seem to have anything in it to help someone at this point. Any suggestions?
2. "You can optionally copy the file conf/quickstarts.properties-example to quickstart.properties"
Could it be changed to "quickstarts/conf/quickstarts.properties-example"? Just to aid dumb users like me.
3. Little typo
"if you want to run the quickstarts against a different server then the one specified in step 1 above."
Shouldn't it be "to"?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBESB-2843) webservice_producer Internal Server Error/500
by Neil Wallace (JIRA)
webservice_producer Internal Server Error/500
---------------------------------------------
Key: JBESB-2843
URL: https://jira.jboss.org/jira/browse/JBESB-2843
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.4 CP2
Reporter: Neil Wallace
Priority: Minor
Fix For: 4.4 CP3
webservice_producer threw this error in ant runtest
saygoodbye_over_http:
[echo] Invoking a JBossWS Endpoint over HTTP (via JBoss ESB).
[java] Calling JBoss Remoting Listener using locator URI: http://localhost:8765
[java] Exception in thread "main" org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Response: Internal Server Error/500.
[java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348)
[java] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
[java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
[java] at org.jboss.remoting.Client.invoke(Client.java:1634)
[java] at org.jboss.remoting.Client.invoke(Client.java:548)
[java] at org.jboss.remoting.Client.invoke(Client.java:536)
[java] at org.jboss.soa.esb.samples.quickstart.webserviceproducer.test.SendMessage.sendMessageToJBRListener(SendMessage.java:75)
[java] at org.jboss.soa.esb.samples.quickstart.webserviceproducer.test.SendMessage.main(SendMessage.java:117)
[java] Caused by: java.lang.NullPointerException
[java] at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:526)
[java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:307)
[java] ... 7 more
BUILD FAILED
/home/nwallace/jboss-soa-p.4.3.0/jboss-as/samples/quickstarts/webservice_producer/build.xml:34: The following error occurred while executing this line:
/home/nwallace/jboss-soa-p.4.3.0/jboss-as/samples/quickstarts/webservice_producer/build.xml:48: Java returned: 1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBESB-2580) The use of EBWS service can interfere with deployment of war packaged inside ESB
by Jiri Pechanec (JIRA)
The use of EBWS service can interfere with deployment of war packaged inside ESB
--------------------------------------------------------------------------------
Key: JBESB-2580
URL: https://jira.jboss.org/jira/browse/JBESB-2580
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta, Web Services
Affects Versions: 4.4 CP2
Reporter: Jiri Pechanec
Priority: Minor
I have en ESB file that contains EBWS. Moreover the ESB also contains WAR file inside to be deployed.
During deployment I get the exception
2009-05-21 13:08:02,831 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/home/jpechane/testing/esbtests/tests/quickstarts/tests/output/lib/Performance_ebwsproxy.esb
org.jboss.deployment.DeploymentException: Error during create of ESB Module: file:/home/jpechane/testing/esbtests/tests/quickstarts/tests/output/lib/Performance_ebwsproxy.esb; - nested throwable: (org.jboss.deployment.DeploymentException: Duplicate subDeployment name: Performance_ebwsproxy.war)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer.create(JBoss4ESBDeployer.java:395)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:566)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
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.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.deployment.DeploymentException: Duplicate subDeployment name: Performance_ebwsproxy.war
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer.create(JBoss4ESBDeployer.java:344)
... 58 more
It is caused by ESB to internally generating war file with the same name as is the ESB package - as visible from JMX console
jboss.web.deployment
id=-1124246638,war=web-console.war
id=-1342401103,war=Performance_ebwsproxy.war
id=-1609398172,war=jbossws-context.war
id=-2023986111,war=Performance_ebwsproxy.war
id=-301626075,war=jbpm-console.war
id=-414077734,war=juddi.war
id=-835178978,war=invoker.war
id=1789078566,war=ROOT.war
id=587009610,war=contract.war
id=792752244,war=jmx-console.war
id=972266901,war=jbossesb.war
If it then later tries to deploy embedded WAR file that has the same name as ESB package the deployment fails with very misleading message
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months