[JBoss JIRA] Created: (JBESB-1274) Support explicit MEP specification
by Kevin Conner (JIRA)
Support explicit MEP specification
----------------------------------
Key: JBESB-1274
URL: http://jira.jboss.com/jira/browse/JBESB-1274
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1 IR2
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.1
At present a one-way action pipeline is supported by having one action in the pipeline return a null message to indicate termination.
There have been numerous one-way services where this was not done, resulting in spurious messages being returned to unsuspecting services.
We need to support an explicit specification of the mep so that actions are free to return a message without concern over the outcome of the pipeline processing.
--
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, 8 months
[JBoss JIRA] Created: (JBESB-832) ${jboss.bind.address} support in ESB configuration files
by Matt Hicks (JIRA)
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL: http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Mark Little
Fix For: 4.2 Milestone Release 3
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh -c esb -b 172.17.0.1). However, there are several problems with the ESB configuration when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to '${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or might need to be converted to XML to have the property replaced.
--
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, 8 months
[JBoss JIRA] Created: (JBESB-1213) bpm_orchestration3 : end state should give clean message, not exception
by Tom Cunningham (JIRA)
bpm_orchestration3 : end state should give clean message, not exception
-----------------------------------------------------------------------
Key: JBESB-1213
URL: http://jira.jboss.com/jira/browse/JBESB-1213
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1 IR2
Reporter: Tom Cunningham
Assigned To: Mark Little
Fix For: 4.2.1
If you signal the process past the number of services nodes, then you get an exception (seen below) - we should catch this and give some feedback to the user that the process instance is now at the end state:
3:00:00,509 ERROR [CommandInterpreter] couldn't execute org.jbpm.command.SignalCommand@29e18a
org.jbpm.JbpmException: couldn't execute org.jbpm.command.SignalCommand@29e18a
at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:73)
at org.jboss.soa.esb.services.jbpm.actions.CommandInterpreter.doTheJob(CommandInterpreter.java:139)
at org.jboss.soa.esb.services.jbpm.actions.impl.DefaultCommandExecutorFactoryImpl$8.execute(DefaultCommandExecutorFactoryImpl.java:291)
at org.jboss.soa.esb.services.jbpm.actions.CommandInterpreter.process(CommandInterpreter.java:80)
at org.jboss.soa.esb.services.jbpm.actions.BpmProcessor.process(BpmProcessor.java:64)
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.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:273)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303)
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:613)
Caused by: org.jbpm.JbpmException: couldn't signal token 'Token(/)' : node 'EndState(end-state1)' doesn't have a default transition
at org.jbpm.graph.exe.Token.signal(Token.java:138)
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.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$5674f18e.signal(<generated>)
at org.jbpm.command.SignalCommand.execute(SignalCommand.java:91)
at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:71)
... 15 more
23:00:00,509 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_bpm_orchestration3_signal_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-12303 RelatesTo: jms:correlationID#ID:JBM-16384 ]
org.jboss.soa.esb.actions.ActionProcessingException: couldn't execute org.jbpm.command.SignalCommand@29e18a
at org.jboss.soa.esb.services.jbpm.actions.CommandInterpreter.process(CommandInterpreter.java:85)
at org.jboss.soa.esb.services.jbpm.actions.BpmProcessor.process(BpmProcessor.java:64)
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.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:273)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303)
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:613)
Caused by: org.jbpm.JbpmException: couldn't execute org.jbpm.command.SignalCommand@29e18a
at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:73)
at org.jboss.soa.esb.services.jbpm.actions.CommandInterpreter.doTheJob(CommandInterpreter.java:139)
at org.jboss.soa.esb.services.jbpm.actions.impl.DefaultCommandExecutorFactoryImpl$8.execute(DefaultCommandExecutorFactoryImpl.java:291)
at org.jboss.soa.esb.services.jbpm.actions.CommandInterpreter.process(CommandInterpreter.java:80)
... 12 more
Caused by: org.jbpm.JbpmException: couldn't signal token 'Token(/)' : node 'EndState(end-state1)' doesn't have a default transition
at org.jbpm.graph.exe.Token.signal(Token.java:138)
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.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$5674f18e.signal(<generated>)
at org.jbpm.command.SignalCommand.execute(SignalCommand.java:91)
at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:71)
... 15 more
23:00:00,510 WARN [ActionProcessingPipeline] No fault address defined for fault message! header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_bpm_orchestration3_signal_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-12303 RelatesTo: jms:correlationID#ID:JBM-16384 ]
--
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, 8 months
[JBoss JIRA] Created: (JBESB-1230) webservice_wssecurity needs better dependency checks
by Tom Cunningham (JIRA)
webservice_wssecurity needs better dependency checks
----------------------------------------------------
Key: JBESB-1230
URL: http://jira.jboss.com/jira/browse/JBESB-1230
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1 IR2
Reporter: Tom Cunningham
Assigned To: Mark Little
Fix For: 4.2.1
Tried to compile webservice_wssecurity against an unpatched ESB server. This QS requires JBoss WS and a remoting patch - there should be some dependency checking here and a message informing the user of the dependencies and how to install.
compile:
[mkdir] Created dir: /Users/tcunning/src/esb/trunk/product/samples/quickstarts/webservice_wssecurity/build/classes
[javac] Compiling 4 source files to /Users/tcunning/src/esb/trunk/product/samples/quickstarts/webservice_wssecurity/build/classes
[javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/webservice_wssecurity/src/org/jboss/test/ws/jaxws/samples/wssecurity/HelloJavaBean.java:30: package org.jboss.ws.annotation does not exist
[javac] import org.jboss.ws.annotation.EndpointConfig;
[javac] ^
[javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/webservice_wssecurity/src/org/jboss/test/ws/jaxws/samples/wssecurity/client/WSSClient.java:22: package org.jboss.ws.core does not exist
[javac] import org.jboss.ws.core.StubExt;
[javac] ^
[javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/webservice_wssecurity/src/org/jboss/test/ws/jaxws/samples/wssecurity/HelloJavaBean.java:33: cannot find symbol
[javac] symbol: class EndpointConfig
[javac] @EndpointConfig(configName = "Standard WSSecurity Endpoint")
[javac] ^
[javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/webservice_wssecurity/src/org/jboss/test/ws/jaxws/samples/wssecurity/client/WSSClient.java:59: cannot find symbol
[javac] symbol : class StubExt
[javac] location: class org.jboss.test.ws.jaxws.samples.wssecurity.client.WSSClient
[javac] ((StubExt) endpoint).setSecurityConfig("jboss-wsse-client.xml");
[javac] ^
[javac] /Users/tcunning/src/esb/trunk/product/samples/quickstarts/webservice_wssecurity/src/org/jboss/test/ws/jaxws/samples/wssecurity/client/WSSClient.java:60: cannot find symbol
[javac] symbol : class StubExt
[javac] location: class org.jboss.test.ws.jaxws.samples.wssecurity.client.WSSClient
[javac] ((StubExt) endpoint).setConfigName("Standard WSSecurity Client");
[javac] ^
[javac] 5 errors
--
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, 8 months
[JBoss JIRA] Created: (JBESB-1260) helloworld_ftp_action & static_router don't display the file contents
by Burr Sutter (JIRA)
helloworld_ftp_action & static_router don't display the file contents
---------------------------------------------------------------------
Key: JBESB-1260
URL: http://jira.jboss.com/jira/browse/JBESB-1260
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1 IR2
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2.1
I didn't have long to look at each one but they just pump lots of DEBUG messages to the console and never display the actual file contents
[qsjava] 15:00:02,593 DEBUG [DefaultQuartzScheduler_QuartzSchedulerThread][Si
mpleJobFactory] Producing instance of Job 'JBossESB.org.jboss.soa.esb.listeners.
gateway.RemoteGatewayListener@1e0512a5-1', class=org.jboss.soa.esb.schedule.Sche
duleProvider$ESBScheduledJob
[qsjava] 15:00:02,593 DEBUG [DefaultQuartzScheduler_Worker-1][JobRunShell] Ca
lling execute on job JBossESB.org.jboss.soa.esb.listeners.gateway.RemoteGatewayL
istener@1e0512a5-1
This debug statement should be turned off and we'll need to figure out why System.out.println(message.getBody().get()); doesn't display the file contents. I suspect the gateway is putting the data in the "wrong" location of the message.
--
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, 8 months
[JBoss JIRA] Created: (JBESB-1228) webservice_consumer throws exceptions
by Tom Cunningham (JIRA)
webservice_consumer throws exceptions
-------------------------------------
Key: JBESB-1228
URL: http://jira.jboss.com/jira/browse/JBESB-1228
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1 IR2
Reporter: Tom Cunningham
Assigned To: Mark Little
Fix For: 4.2.1
webservice_consumer1 QS throws exceptions on runtest - this was run on a clean ESB server :
11:15:53,172 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
11:15:53,172 INFO [STDOUT] Request map is: {sayHello.toWhom=Jimbo}
11:15:53,172 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
11:15:53,173 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_webservice_consumer1_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_webservice_consumer1_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='e0bae669-808a-4d44-b759-bf553eb7be7f'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-512 RelatesTo: jms:correlationID#b8e0f97f-efb1-4436-9133-4d4b94e2c7ff ]
java.lang.ClassCastException: java.lang.String
at org.jboss.soa.esb.actions.soap.SOAPClient.process(SOAPClient.java:321)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:273)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303)
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: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, 8 months