June 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3817) Change bpm5processor Quickstart to show off ESBWorkItemHandler

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3817: ------------------------------------- Summary: Change bpm5processor Quickstart to show off ESBWorkItemHandler Key: JBESB-3817 URL: https://issues.jboss.org/browse/JBESB-3817 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Change the bpm5processor action so that it shows off the ESBWorkItemHandler. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3816) Get an HibernateException in JbpmJobExector when starting 4.11 out of the box

by Olle Sundblad (JIRA)

Olle Sundblad created JBESB-3816: ------------------------------------ Summary: Get an HibernateException in JbpmJobExector when starting 4.11 out of the box Key: JBESB-3816 URL: https://issues.jboss.org/browse/JBESB-3816 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.11 Environment: Windows 7 Reporter: Olle Sundblad When I download and install (unzip) the 4.11 release and start it using run.bat without any changes whatsoever I get the following stacktrace over and over again. end of start console (it started with no errors/warnings): 09:57:16,666 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 09:57:16,677 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 28s:270ms but immediately after I get the following: 09:57:31,928 INFO [Configuration] configuring from resource: hibernate.cfg.xml 09:57:31,929 INFO [Configuration] Configuration resource: hibernate.cfg.xml 09:57:52,939 INFO [Configuration] configuring from resource: hibernate.cfg.xml 09:57:52,940 INFO [Configuration] Configuration resource: hibernate.cfg.xml 09:57:52,939 ERROR [LockMonitorThread] exception in JbpmJobExector@138.106.178.133:Monitor org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1494) at org.hibernate.cfg.Configuration.configure(Configuration.java:1428) at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104) at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93) at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100) at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88) at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50) at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61) at org.jbpm.svc.Services.getService(Services.java:160) at org.jbpm.svc.Services.getPersistenceService(Services.java:197) at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695) at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639) at org.jbpm.job.executor.LockMonitorThread.unlockOverdueJobs(LockMonitorThread.java:64) at org.jbpm.job.executor.LockMonitorThread.run(LockMonitorThread.java:43) Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1484) ... 15 more This repeats over and over again until I stop the server. I do not get this exception in 4.10 (so my unqualified guess is the jbpm5 stuff is missing the hibernate.cfg.xml or something) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
1
0 / 0

[JBoss JIRA] (JBESB-3792) Bpm5Processor does not map BPM parameters on SIGNAL_EVENT.

by Marek Baluch (JIRA)

Marek Baluch created JBESB-3792: ----------------------------------- Summary: Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. Key: JBESB-3792 URL: https://issues.jboss.org/browse/JBESB-3792 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Reporter: Marek Baluch Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. This means that settings like: {code} <action name="jbpm5-2" class="org.jboss.soa.esb.services.jbpm5.actions.Bpm5Processor"> <property name="process-definition-name" value="Evaluation.bpmn"/> <property name="process-id" value="com.sample.evaluation"/> <property name="process-action" value="signalEvent|abortProcessInstance"/> <property name="esbToBpmParams"> <mapping esb="employee" bpm="employee" value="krisv"/> <mapping esb="reason" bpm="reason" value="Yearly performance review"/> </property> </action> {code} have no effect. IMO mapping BPM parameters does not make much sense for the abortProcessInstance (as used in the bpm5processor sample) event but it makes sence for signalEvent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
7
0 / 0

[JBoss JIRA] (JBESB-3815) Fix ClassCastException in ServiceRouteFilter

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3815: ------------------------------------- Summary: Fix ClassCastException in ServiceRouteFilter Key: JBESB-3815 URL: https://issues.jboss.org/browse/JBESB-3815 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Fix ClassCastException here in ServiceRouteFilter : String gatewayConfig = (String) params.get(Environment.GATEWAY_CONFIG); Also add the address of the server into the route. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3814) EBWS contract's HTTPS urls are not re-written using that protocol and address

by Magesh Bojan (JIRA)

Magesh Bojan created JBESB-3814: ----------------------------------- Summary: EBWS contract's HTTPS urls are not re-written using that protocol and address Key: JBESB-3814 URL: https://issues.jboss.org/browse/JBESB-3814 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.11 Reporter: Magesh Bojan Although the address works for WSDL and endpoints, they are not displayed with https urls when access via https://localhost:8443/contract/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] (JBESB-3812) When multiple SOAPProcessor actions are used in one pipeline the second call sends an invalid 'Content-type' header

by Jason Shepherd (JIRA)

Jason Shepherd created JBESB-3812: ------------------------------------- Summary: When multiple SOAPProcessor actions are used in one pipeline the second call sends an invalid 'Content-type' header Key: JBESB-3812 URL: https://issues.jboss.org/browse/JBESB-3812 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 Environment: SOA-P 5.2 Reporter: Jason Shepherd Priority: Minor Attachments: webservice_multi_producer.zip When multiple SOAPProcessors are used in a action processing pipeline, the second call will send an invalid 'Content-type' header, which will cause the second wrapper webservice to fail with the following message: 2012-06-01 16:37:26,453 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (pool-88-thread-1) SOAP request exception javax.xml.soap.SOAPException: Could not parse content type:javax.mail.internet.ParseException: Expected '/', got @ at org.jboss.ws.core.soap.MessageFactoryImpl.getContentType(MessageFactoryImpl.java:318) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:212) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:451) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:294) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:203) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:129) at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:550) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2012