[JBoss JIRA] Created: (JBESB-2255) Unresponsive EPR: JMSEpr when service invoker is put under load
by Daniel Bevenius (JIRA)
Unresponsive EPR: JMSEpr when service invoker is put under load
---------------------------------------------------------------
Key: JBESB-2255
URL: https://jira.jboss.org/jira/browse/JBESB-2255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.5
When load testing using the webservice_producer quickstart (using soapui loadtest: threads: 50, Limit:200 Total runs.
The server console will print:
13:32:34,050 INFO [ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <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='25704ae2-adb1-496e-bd79-4000bd68b268'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]
13:32:34,124 INFO [ServiceInvoker] Badly formed EPR [EPR: PortReference < <wsa:Address http://localhost:8765/> >] for Service [MyServiceCategory:MyWSProducerService] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <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='25704ae2-adb1-496e-bd79-4000bd68b268'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]].Courier for EPR not supported: ESB-unaware EPR used!
13:32:34,137 INFO [ServiceInvoker] Invalid EPR for service (probably ESB-unaware): ignoring for message: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <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='25704ae2-adb1-496e-bd79-4000bd68b268'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]
13:32:34,138 INFO [ServiceInvoker] Badly formed EPR [EPR: PortReference < <wsa:Address http://localhost:8765/> >] for Service [MyServiceCategory:MyWSProducerService] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <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='25704ae2-adb1-496e-bd79-4000bd68b268'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]].Courier for EPR not supported: ESB-unaware EPR used!
13:32:34,139 INFO [ServiceInvoker] Invalid EPR for service (probably ESB-unaware): ignoring for message: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_webservice_producer_esb_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <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='25704ae2-adb1-496e-bd79-4000bd68b268'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]
And in server.log:
2008-12-30 13:32:36,205 DEBUG [org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool] The connection pool was exhausted, waiting for a session to be released.
--
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
15 years, 9 months
[JBoss JIRA] Created: (JBESB-2251) PermGen Error when accessing the contract web application containing a webservice
by Daniel Bevenius (JIRA)
PermGen Error when accessing the contract web application containing a webservice
---------------------------------------------------------------------------------
Key: JBESB-2251
URL: https://jira.jboss.org/jira/browse/JBESB-2251
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management, Web Services
Reporter: Daniel Bevenius
Priority: Critical
Fix For: 4.5
I noticed this when using the esb server the main trunk and when deploying a webservice.
For example, deploying the webservice_producer quickstart and then accessing the contract for the http transport at http://localhost:8080/contract will produce this error:
13:08:04,200 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/compiler/lookup/MethodVerifier
at org.eclipse.jdt.internal.compiler.Compiler.<init>(Compiler.java:257)
at org.eclipse.jdt.internal.compiler.Compiler.<init>(Compiler.java:149)
at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:399)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:308)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:316)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
13:08:06,634 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space
13:08:10,113 ERROR [STDERR] at sun.misc.Unsafe.defineClass(Native Method)
13:08:10,113 ERROR [STDERR] at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45)
13:08:10,113 ERROR [STDERR] at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381)
13:08:10,113 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method)
13:08:10,113 ERROR [STDERR] at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377)
13:08:10,113 ERROR [STDERR] at sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95)
13:08:10,113 ERROR [STDERR] at sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313)
13:08:10,113 ERROR [STDERR] at java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1299)
13:08:10,113 ERROR [STDERR] at java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52)
13:08:10,113 ERROR [STDERR] at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:420)
13:08:10,113 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method)
13:08:10,113 ERROR [STDERR] at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:400)
13:08:10,113 ERROR [STDERR] at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:297)
13:08:10,113 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1035)
13:08:10,113 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
13:08:10,113 ERROR [STDERR] at sun.rmi.server.MarshalOutputStream.writeLocation(MarshalOutputStream.java:91)
13:08:10,113 ERROR [STDERR] at sun.rmi.server.MarshalOutputStream.annotateClass(MarshalOutputStream.java:75)
13:08:10,113 ERROR [STDERR] at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1174)
13:08:10,113 ERROR [STDERR] at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1127)
13:08:10,113 ERROR [STDERR] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)
13:08:10,113 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
13:08:10,114 ERROR [STDERR] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
13:08:10,114 ERROR [STDERR] at sun.rmi.server.UnicastRef.marshalValue(UnicastRef.java:258)
13:08:10,114 ERROR [STDERR] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117)
13:08:10,114 ERROR [STDERR] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
13:08:10,114 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
13:08:10,114 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
13:08:10,114 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351)
13:08:10,114 ERROR [STDERR] at org.jbpm.persistence.jta.JtaDbPersistenceService.getUserTransaction(JtaDbPersistenceService.java:88)
13:08:10,114 ERROR [STDERR] at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:49)
13:08:10,114 ERROR [STDERR] at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:28)
13:08:10,114 ERROR [STDERR] at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:17)
13:08:10,114 INFO [JobExecutorThread] JbpmJobExector:127.0.1.1:1 leaves cyberspace
Doing the same with the binary distribution of jbossesb-server4.4.GA does not produce this issue.
--
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
15 years, 9 months
[JBoss JIRA] Created: (JBESB-2231) </mbean> missing in bpm_orchestration1 jbm-queue-service.xml example file
by David Parry (JIRA)
</mbean> missing in bpm_orchestration1 jbm-queue-service.xml example file
-------------------------------------------------------------------------
Key: JBESB-2231
URL: https://jira.jboss.org/jira/browse/JBESB-2231
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.4
Environment: Windows jbossesb-4.4.GA\samples\quickstarts\bpm_orchestration1
Reporter: David Parry
Priority: Trivial
The </mbean> tag is missing for the the jbossesb-4.4.GA\samples\quickstarts\bpm_orchestration example in file jbm-queue-service.xml. This causes a deploy error of the .esb file when running ant deploy from jbossesb-4.4.GA\samples\quickstarts\bpm_orchestration1.
I added it and the example works the missing tag should be on line 44 of jbm-queue-service.xml.
Sorry would check it in but dont have rights cheers hope this helps others
--
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
15 years, 9 months
[JBoss JIRA] Created: (JBESB-2054) Service and Category names accept only TitleCase throws "Unexpected EOF in prolog" when not so
by Magesh Kumar B (JIRA)
Service and Category names accept only TitleCase throws "Unexpected EOF in prolog" when not so
----------------------------------------------------------------------------------------------
Key: JBESB-2054
URL: https://jira.jboss.org/jira/browse/JBESB-2054
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1 CP3
Environment: SOA-P 4.2.0.GA_CP02
Reporter: Magesh Kumar B
Priority: Minor
Attachments: simpleEsb.esb
When the service is declared as small case the EPR is not registered and the findEPR returns empty XML string. So the following exception is thrown:
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661)
at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at org.jboss.internal.soa.esb.util.stax.StreamHelper.skipToStartElement(StreamHelper.java:317)
at org.jboss.internal.soa.esb.addressing.helpers.EPRHelper.fromXMLString(EPRHelper.java:139)
See attached simpleEsb.esb
--
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
15 years, 9 months
[JBoss JIRA] Created: (JBESB-1881) DataFiler errors on trunk
by Tom Cunningham (JIRA)
DataFiler errors on trunk
-------------------------
Key: JBESB-1881
URL: https://jira.jboss.org/jira/browse/JBESB-1881
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.4
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Burr sees the following on trunk:
17:00:03,296 ERROR [DataFiler] ERROR - found type of java.lang.Integer for actio
n bytes failed
17:00:03,298 ERROR [DataFiler] ERROR - found type of java.lang.Integer for actio
n bytes processed
17:00:03,304 ERROR [DataFiler] ERROR - found type of java.lang.Integer for overa
ll bytes processed
17:00:03,307 ERROR [DataFiler] ERROR - found type of java.lang.Integer for overa
ll bytes failed
17:00:03,373 ERROR [DataFiler] ERROR - found type of java.lang.Integer for testS
tore bytes failed
17:00:03,375 ERROR [DataFiler] ERROR - found type of java.lang.Integer for setup
Key bytes failed
--
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
15 years, 9 months