[JBoss JIRA] (JBESB-3840) http-gateway returns invalid empty WSDL document.
by Marek Baluch (JIRA)
Marek Baluch created JBESB-3840:
-----------------------------------
Summary: http-gateway returns invalid empty WSDL document.
Key: JBESB-3840
URL: https://issues.jboss.org/browse/JBESB-3840
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.11 CP1
Reporter: Marek Baluch
When an ESB application is deployed and this application contains a service like:
{code}
<service category="Sales" name="List" description="" invmScope="GLOBAL">
<listeners>
<!-- Receives: http://<host>:<port>/Quickstart_http_gateway/http/sales/* but will be forced to
authenticate because the "sales" bus has basic auth configured (above)... -->
<http-gateway name="sales" busidref="secureFriends" urlPattern="sales/*" />
</listeners>
<actions mep="RequestResponse">
<action name="print" class="org.jboss.soa.esb.samples.quickstart.httpgateway.MyAction"/>
</actions>
</service>
{code}
then the URL http://<host>:<port>/Quickstart_http_gateway/http/sales?wsdl returns the following WSDL document:
{code}
<definitions/>
{code}
which clearly is not valid since it's not in the correct namespace. Even more in my opinion the http-gateway should
not return a WSDL document by default since it may be used with more then SOAP.
--
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
13 years, 6 months
[JBoss JIRA] (JBESB-3861) Update commons-codec libraries
by Martin Weiler (JIRA)
Martin Weiler created JBESB-3861:
------------------------------------
Summary: Update commons-codec libraries
Key: JBESB-3861
URL: https://issues.jboss.org/browse/JBESB-3861
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.11
Reporter: Martin Weiler
We're getting this exception when we're trying to send a large (>200Mb) message to a subsequent action. Full stacktrace follows:
ERROR [org.jboss.soa.esb.client.ServiceInvoker] (pool-58-thread-1) Unexpected throwable during attempted message delivery using Courier for EPR [JMSEpr ... ]].
java.lang.NegativeArraySizeException
at org.apache.commons.codec.binary.Base64.encodeBase64(Base64.java:258)
at org.apache.commons.codec.binary.Base64.encodeBase64(Base64.java:178)
at org.jboss.internal.soa.esb.util.Encoding.encodeBytes(Encoding.java:43)
at org.jboss.internal.soa.esb.util.Encoding.encodeObject(Encoding.java:62)
at org.jboss.internal.soa.esb.message.format.xml.marshal.SerializedMarshalUnmarshalPlugin.marshal(SerializedMarshalUnmarshalPlugin.java:83)
at org.jboss.internal.soa.esb.message.format.xml.marshal.MarshalUnmarshalManager.marshal(MarshalUnmarshalManager.java:145)
at org.jboss.internal.soa.esb.message.format.xml.BodyImpl.writeChildContent(BodyImpl.java:146)
at org.jboss.internal.soa.esb.util.stax.ElementContent.writeContent(ElementContent.java:41)
at org.jboss.internal.soa.esb.util.stax.StreamHelper.writeElement(StreamHelper.java:125)
at org.jboss.internal.soa.esb.message.format.xml.MessageImpl.writeChildContent(MessageImpl.java:236)
at org.jboss.internal.soa.esb.util.stax.ElementContent.writeContent(ElementContent.java:41)
at org.jboss.soa.esb.util.Util.serialize(Util.java:188)
at org.jboss.internal.soa.esb.couriers.JmsCourier.internalDeliver(JmsCourier.java:224)
at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:187)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:189)
at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:702)
at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:604)
at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:392)
at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:265)
An upgrade of the commons-codec libraries from the currently bundled version 1.3 includes a fix for CODEC-61 [1]. This would allow to Base64 encode input data up to 2GB, instead of the ~250MB limitation in common codecs version 1.3.
[1] https://issues.apache.org/jira/browse/CODEC-61
--
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
13 years, 6 months
[JBoss JIRA] (JBESB-3859) Uncommenting GenericPipelineInterceptors in jbossesb-properties.xml causes NullPointerException at startup
by Tom Cunningham (JIRA)
Tom Cunningham created JBESB-3859:
-------------------------------------
Summary: Uncommenting GenericPipelineInterceptors in jbossesb-properties.xml causes NullPointerException at startup
Key: JBESB-3859
URL: https://issues.jboss.org/browse/JBESB-3859
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.11
Reporter: Tadayoshi Sato
When the following "interceptors" properties in jbossesb-properties.xml are uncommented, the JBoss ESB throws java.lang.NullPointerException and fails to start up.
{code:xml}
<properties name="interceptors">
<property name="org.jboss.soa.esb.pipeline.failure.interceptors" value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/>
<property name="org.jboss.soa.esb.pipeline.instantiate.interceptors" value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/>
<property name="org.jboss.soa.esb.pipeline.start.interceptors" value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/>
<property name="org.jboss.soa.esb.pipeline.end.interceptors" value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/>
</properties>
{code}
The error stacktrace is as follows:
{code}
2012-10-15 14:50:42,708 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss.esb.vfsfile:/opt/jboss-soa-p-5.3.0/jboss-as/server/default/deploy/jbossesb.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:231)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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:243)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:111)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72)
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:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:223)
at org.jboss.Main$1.run(Main.java:574)
at java.lang.Thread.run(Thread.java:722)
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.getListeners(LifecycleUtil.java:76)
at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:124)
... 63 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at org.jboss.soa.esb.listeners.LifecycleUtil.getManagedInstances(LifecycleUtil.java:162)
... 65 more
Caused by: java.lang.NullPointerException
at org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor.processMessage(GenericPipelineInterceptor.java:33)
at org.jboss.soa.esb.listeners.message.InterceptorManager.interceptInstantiate(InterceptorManager.java:126)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.<init>(ActionProcessingPipeline.java:381)
at org.jboss.soa.esb.listeners.ScheduleListener.<init>(ScheduleListener.java:90)
... 70 more
2012-10-15 14:50:42,710 INFO [org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment] (main) Destroying 'jbossesb.esb'
{code}
--
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
13 years, 6 months
[JBoss JIRA] (JBESB-3856) IterableTimedCache expiry causes deployment issues with Camel non-core components
by Tom Cunningham (JIRA)
Tom Cunningham created JBESB-3856:
-------------------------------------
Summary: IterableTimedCache expiry causes deployment issues with Camel non-core components
Key: JBESB-3856
URL: https://issues.jboss.org/browse/JBESB-3856
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 4.11
Environment:
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.11 CP1
There's a problem with deployment of esb application, where the camel gateway is used .
If is the application deployed right after the server start, there's no problem. But if you wait about 30-60 minutes, error occurs, and about 100 of this error message are shown:
DEBUG [JBossPackageScanClassResolver] Cannot find class 'apache/camel/converter/stream/InputStreamCache.class' in any classloaders: [BaseClassLoader@2444569{vfszip:/home/rbalent/qa/tests/quickstarts/tests/output/lib/Quickstart_camel_http.esb/}]
To see the messages you must set log threshold to DEBUG.
To reproduce it, just start server, deploy attached Quickstart_camel_http.esb, then you will see the correct message in server log:
BEFORE**
Camel HTTP Hello World!
AFTER**
Lines "BEFORE**", and "AFTER**" are added to find the message body in server log easier.
then undeploy Quickstart_camel_http.esb and wait about 30-60 minutes. After this time, deploy the esb package again. You will see the mentioned lines in server log, and incorrect message body:
The received message will look like this:
BEFORE**
java.io.ByteArrayInputStream@6c515139AFTER**
After server restart it works again.
Quickstart_camel_http.esb, server log of successful deployment and failed deployment are attached.
--
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
13 years, 6 months
[JBoss JIRA] (JBESB-3854) NPE in SqlTableGatewayListener when Oracle goes down
by Tom Cunningham (JIRA)
Tom Cunningham created JBESB-3854:
-------------------------------------
Summary: NPE in SqlTableGatewayListener when Oracle goes down
Key: JBESB-3854
URL: https://issues.jboss.org/browse/JBESB-3854
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.9 CP2
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.9 CP2
Description of problem:
Listener is not fetching the data from the database after the Data source disconnect and reconnect. To resolve the issue we have to redeploy the esb.
Version-Release number of selected component (if applicable):
JBoss SOA-P 5.2.0
How reproducible:
always
Steps to Reproduce:
1. deploy ESB project which uses SQL listener
2. restart database, wait few minutes
3. notice that SQL listener is stopped
Actual results:
SQL listener not polling
Expected results:
SQL listener polling
Additional info:
Proposed fix:
Index: src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java
===================================================================
--- src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java (revision 37737)
+++ src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java (working copy)
@@ -507,7 +507,7 @@
RS.close();
oConn.rollback();
- } catch (final SQLException sqle) {
+ } catch (Exception ex) {
refreshDatasource();
}
--
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
13 years, 7 months