[JBoss JIRA] Created: (JBESB-1058) jbossesb console is showing wrong charts
by Martin Vecera (JIRA)
jbossesb console is showing wrong charts
----------------------------------------
Key: JBESB-1058
URL: http://jira.jboss.com/jira/browse/JBESB-1058
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tooling
Affects Versions: 4.2.1 IR1
Environment: Sun JVM, ant 1.6.5, Firefox browser
Reporter: Martin Vecera
Assigned To: Mark Little
I can see wrong charts in jbossesb console (management.esb - localhost:8080/jbossesb/).
Steps to reproduces:
1. click on 'RedeliverMessagesAction messages successfully processed count'
2. immediately click on 'Back to Console index'
3. immediately click on 'RedeliverMessagesAction processing time'
4. you can still see chart for 'RedeliverMessagesAction messages successfully processed count'
5. reload the page to see correct chart (sometimes needs to be reloaded several times)
The problem is that the 'random number' in chart image name is not random. It is all the time the same in my case.
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBESB-1094) .ESB archives should support service.xml files
by Tom Cunningham (JIRA)
.ESB archives should support service.xml files
----------------------------------------------
Key: JBESB-1094
URL: http://jira.jboss.com/jira/browse/JBESB-1094
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 4.2
Reporter: Tom Cunningham
Assigned To: Mark Little
Currently .ESB archives do not support service.xml files. We use these service.xml files a lot of times to do once-only database schema creation (conditional upon some query, see attached file for example). It'd be nice if .ESB archives supported this - it would make completely undeploying something like the monitoring console easier - the monitoring console has an .esb file and a service.xml which is free floating in server/<default>/deploy.
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBESB-1060) The ESB throws NullPointerEception when there are no variables passed to jBPM process
by Jiri Pechanec (JIRA)
The ESB throws NullPointerEception when there are no variables passed to jBPM process
-------------------------------------------------------------------------------------
Key: JBESB-1060
URL: http://jira.jboss.com/jira/browse/JBESB-1060
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.2
Reporter: Jiri Pechanec
Assigned To: Mark Little
If you will not pass any variable but body when starting jBPM process then you will receive following exception
org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:265)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297)
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)
Caused by: java.lang.NullPointerException
at org.jboss.soa.esb.services.jbpm.actions.impl.facades.FacadeUtil.jbpmVarsToMessage(FacadeUtil.java:139)
at org.jboss.soa.esb.services.jbpm.actions.impl.facades.NewProcessInstanceFacade.postFormat(NewProcessInstanceFacade.java:84)
at org.jboss.soa.esb.services.jbpm.actions.BpmProcessor.process(BpmProcessor.java:65)
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)
... 6 more
The reason is that FacadeUtil expects that jBPM will return empty map when there are no variables in the context. Unfortuanetly for jBPM is valid to return even the null value when the variable list do not contain any variables.
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBESB-786) Change Gateways so they don't always use the byte[] portion of Messages
by Mark Little (JIRA)
Change Gateways so they don't always use the byte[] portion of Messages
-----------------------------------------------------------------------
Key: JBESB-786
URL: http://jira.jboss.com/jira/browse/JBESB-786
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Mark Little
Sometimes byte[] may make sense, but for a lot of cases it simply doesn't. For example, using setByteArray for sending back a String! For incoming messages (small 'm') we could allow for header encoding within the received stream that indicates how the message (small 'm') should then we encapsulated within the ESB as a Message. That would mean we wouldn't convert all incoming byte streams as byte streams in the ESB either.
--
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
17 years, 2 months