September 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3849) Exception when deploying fs-provider without input-suffix and post-delete set to true

by Lennart Petersson (JIRA)

Lennart Petersson created JBESB-3849: ---------------------------------------- Summary: Exception when deploying fs-provider without input-suffix and post-delete set to true Key: JBESB-3849 URL: https://issues.jboss.org/browse/JBESB-3849 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Environment: Mac OS X Mountain Lion Reporter: Lennart Petersson Using sample helloworld_file_action. When trying to deploy this sample WITHOUT using input-suffix and setting post-delete to TRUE we got a deployment exception: 23:39:52,071 ERROR [AbstractKernelController] Error installing to Start: name=jboss.esb.vfszip:/Users/lenp/Sources/LiV/jboss/inner/server/default/deploy/Quickstart_helloworld_file_action.esb/ state=Create java.lang.RuntimeException: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected exception while instantiating managed instance at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:185) at org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment.start(EsbDeployment.java:222) 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:597) at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59) at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150) at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241) at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70) at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121) at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) 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:680) Caused by: org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected exception while instantiating managed instance at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(LifecycleUtil.java:166) at org.jboss.soa.esb.listeners.LifecycleUtil.getGateways(LifecycleUtil.java:104) at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:130) ... 55 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(LifecycleUtil.java:162) ... 57 more Caused by: org.jboss.soa.esb.ConfigurationException: Must specify postProcessSuffix at org.jboss.internal.soa.esb.listeners.gateway.filefilter.IgnoreFile.<init>(IgnoreFile.java:45) at org.jboss.soa.esb.listeners.gateway.FileGatewayListener.<init>(FileGatewayListener.java:72) ... 62 more Reason is that in AbstractFileGateway.java (line 317) there is the following code: if (_deleteAfterOK) { return; } And since we have set post-delete to TRUE this will trigger the return. Ok, all fine here - but we are missing an important part that was in the code further below: _postProcessSuffix = ListenerUtil.getValue(config, ListenerTagNames.FILE_POST_SFX_TAG, ".esbDone").trim(); That is, getting the post-suffix from the configuration. Well... you might say that it is not needed since we have post-delete set to TRUE!? Yeah sure, but in the file IgnoreFile.java we find the following row in the constructor (line 44): if (Util.isNullString(_postSuffix)) throw new ConfigurationException("Must specify postProcessSuffix"); And here _postSuffix is null (due to the previous return statement) and hence we have an exception! I've verified a 'solution' that works and that is to add the extraction of the post-suffix configuration just before the return statement in AbstractFileGateway.java file, like this: if (_deleteAfterOK) { _postProcessSuffix = ListenerUtil.getValue(config, ListenerTagNames.FILE_POST_SFX_TAG, ".esbDone").trim(); return; } I've not tested newer versions but looking at the AbstractFileGateway.java file also in 4.11 it looks the same so I guess the problem is also there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3783) SOAPProxy doesn't rewrite SOAP1.2 service port address location in WSDL

by Sato Tadayoshi (JIRA)

Sato Tadayoshi created JBESB-3783: ------------------------------------- Summary: SOAPProxy doesn't rewrite SOAP1.2 service port address location in WSDL Key: JBESB-3783 URL: https://issues.jboss.org/browse/JBESB-3783 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.11 Reporter: Sato Tadayoshi SOAPProxy should rewrite the service port addresses in WSDL provided by a target Web service endpoint from the original URL to ESB's URL. But if the target is a SOAP 1.2 service, SOAPProxy fails to rewrite its SOAP 1.2 address location and the original URL remains to be presented in the WSDL provided by ESB like below: {code:xml|title=WSDL published by ESB} <definitions ... xmlns:soap12='http://schemas.xmlsoap.org/wsdl/soap12/'> ... <service name='GoodbyeWorldWSService'> <port binding='tns:GoodbyeWorldWSBinding' name='GoodbyeWorldWSPort'> <soap12:address location='http://www.acme.com/original/address'/>  </port> </service> </definitions> {code} -- 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, 9 months

4
8
0 / 0

[JBoss JIRA] (JBESB-3848) Add required=false to Connection Properties in JON plugin

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3848: ------------------------------------- Summary: Add required=false to Connection Properties in JON plugin Key: JBESB-3848 URL: https://issues.jboss.org/browse/JBESB-3848 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Cunningham -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
4
0 / 0

[JBoss JIRA] (JBESB-3844) Imported XSDs in WSDL aren rewritten wrongly by JBR Gateway

by Sato Tadayoshi (JIRA)

Sato Tadayoshi created JBESB-3844: ------------------------------------- Summary: Imported XSDs in WSDL aren rewritten wrongly by JBR Gateway Key: JBESB-3844 URL: https://issues.jboss.org/browse/JBESB-3844 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports, Web Services Affects Versions: 4.11 Reporter: Sato Tadayoshi Turning {{'cache-schemas'}} introduced by JBESB-3802 to {{true}} doens't rewrite the schema imports in WSDLs correctly for the JBoss Remoting Gateway. The {{definitions/import/@location}} or the {{definitions/types/schema/import/@schemaLocation}} in a WSDL should be rewritten to: {code} http://localhost:8080/contract/contract.jsp?wsdl&serviceCat=MyCategory&se... {code} but actually: {code} http://localhost:8765/?wsdl&resource=hello.xsd {code} where the JBR gateway is configured at {{http://localhost:8765}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
5
0 / 0

[JBoss JIRA] (JBESB-3845) Rewrite WSDL imports published via JBR / HTTP Gateways to point to locally cached versions

by Sato Tadayoshi (JIRA)

Sato Tadayoshi created JBESB-3845: ------------------------------------- Summary: Rewrite WSDL imports published via JBR / HTTP Gateways to point to locally cached versions Key: JBESB-3845 URL: https://issues.jboss.org/browse/JBESB-3845 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports, Web Services Affects Versions: 4.11 Reporter: Sato Tadayoshi Rewrite of imported XSDs in WSDL is introduced by JBESB-3802, but it rewrites only XML Schema imports ({{<xsd:import schemaLocation=".../xxx.xsd" .../>}}). We also need as well the function to rewrite WSDL imports ({{<import location=".../xxx.{wsdl|xsd}" .../>}}) which can import not only XSDs but also partial WSDLs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3274) Update soapui jar

by Kevin Conner (JIRA)

Update soapui jar ----------------- Key: JBESB-3274 URL: https://jira.jboss.org/jira/browse/JBESB-3274 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.8 Reporter: Kevin Conner The version we use is 1.7.1 and the current version is 3.5. We need to look at updating. -- 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

11 years, 9 months

4
9
0 / 0

[JBoss JIRA] (JBESB-3843) Merge 4.11CP branch back to trunk

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3843: ------------------------------------- Summary: Merge 4.11CP branch back to trunk Key: JBESB-3843 URL: https://issues.jboss.org/browse/JBESB-3843 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Cunningham -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
4
0 / 0

[JBoss JIRA] (JBESB-3842) Message not reaching in remote queue intermittently.

by Rejin M (JIRA)

Rejin M created JBESB-3842: ------------------------------ Summary: Message not reaching in remote queue intermittently. Key: JBESB-3842 URL: https://issues.jboss.org/browse/JBESB-3842 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server, Message Store, Web Services Environment: Linux Reporter: Rejin M I am facing an issue while delivering message to remote queue. My Jboss ESB server is in one linux system and Messaging server in another linux system. After completed all the actionpipeline flow, message is routing to remote queue in messaging server via JMSRouter. Most of the messages are reaching in the remote queue while few are not. For these failed cases, the control is reaching till the JMSRouter, then no respose. Below is my jboss-esb.xml <providers> <jms-provider connection-factory="ConnectionFactory" jndi-URL="jnp://10.38.230.46:1299" name="otp_P2_msg_rec"> <jms-bus busid="otp_P2_jms_channel"> <jms-message-filter dest-name="queue/otp_p2_request_Q" dest-type="QUEUE" jms-security-credential="esbpassword" jms-security-principal="esbuser"/> </jms-bus> </jms-provider> <jms-provider connection-factory="ConnectionFactory" jndi-URL="jnp://10.38.230.46:1299" name="otp_service_setting_change_rec"> <jms-bus busid="otp_service_setting_change_channel"> <jms-message-filter dest-name="topic/settingChange_topic" dest-type="TOPIC" jms-security-credential="esbpassword" jms-security-principal="esbuser"/> </jms-bus> </jms-provider> </providers> <services> <service category="com.emirates.otp_p2" description="OTP Process Flow" invmScope="GLOBAL" name="otp_P2_proc_flow_service"> <property name="maxThreads" value="200"/> <listeners> <jms-listener busidref="otp_P2_jms_channel" is-gateway="true" maxThreads="200" name="otp_P2_process_flow_listener"/> </listeners> <actions mep="OneWay"> <action class="org.jboss.soa.esb.actions.SystemPrintln" name="printPatternType"> <property name="message" value="*********************************P A T T E R N -- 2*******************************"/> </action> <action class="com.emirates.otp.esb.actions.audit.AuditProcessor" name="startAuditProcess" process="startAuditProcess"> <property name="auditQ" value="queue/auditservice_queue"/> </action> <action class="com.emirates.otp.esb.actions.core.OTPInitializer" name="initializeOTPBus" process="process">  </action> <action class="com.emirates.otp.esb.actions.security.AuthenticationProcessor" name="authenticate" process="process"/>  <action class="com.emirates.otp.esb.actions.processor.OtpProcessorAction" name="preProcessor"> <property name="processorType" value="preProcessor"/> <property name="processorLevel" value="preSearch"/> </action> <action class="com.emirates.otp.esb.actions.brms.CustomBusinessRulesProcessor" name="applyFilterRules"> <property name="object-paths"> <object-path esb="body.OTPMessage"/> </property> <property name="command" value="OTP2_RULES_PROP"/> <property name="ruleAgentProperties" value="stpcrules.properties"/> </action> <action class="com.emirates.otp.esb.actions.processor.OtpProcessorAction" name="postProcessor"> <property name="processorType" value="postProcessor"/> <property name="processorLevel" value="postSearch"/> </action>  <action class="com.emirates.otp.esb.actions.audit.AuditProcessor" name="stopAuditProcess2" process="stopAuditProcess"> <property name="auditQ" value="queue/auditservice_queue"/> </action> <action name="print-before-jmsrouter" class="org.jboss.soa.esb.actions.SystemPrintln"> </action> <action class="org.jboss.soa.esb.actions.routing.JMSRouter" name="sendResponse"> <property name="jndiName" value="queue/otp_p2_response_Q"/> <property name="jndi-URL" value="jnp://10.38.230.46:1299"/> <property name="connection-factory" value="ConnectionFactory"/> <property name="unwrap" value="true"/> <property name="persistent" value="false"/> <property name="security-principal" value="esbuser"/> <property name="security-credential" value="esbpassword"/> </action> </actions> </service> -- 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
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2012