October 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1258) helloworld_file_action QS throws 'max-millis-for-response' is not allowed to appear in element

by Burr Sutter (JIRA)

helloworld_file_action QS throws 'max-millis-for-response' is not allowed to appear in element ---------------------------------------------------------------------------------------------- Key: JBESB-1258 URL: http://jira.jboss.com/jira/browse/JBESB-1258 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2.1 triage Fails to deploy as a .esb archive (from SVN Trunk as of oct 27) 14:27:40,609 ERROR [XmlValidatorImpl] 1-ERROR-null-50:cvc-complex-type.3.2.2: At tribute 'max-millis-for-response' is not allowed to appear in element 'fs-listen er'. 14:27:40,640 WARN [ServiceController] Problem starting service jboss.esb:deploy ment=Quickstart_helloworld_file_action.esb java.lang.RuntimeException: java.lang.IllegalStateException: ESB file had valida tion errors. at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration .java:132) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(J Boss4ESBDeployment.java:82) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS upport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl ler.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) -- 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

16 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-1280) CLONE -Base64 encode "swallows" serialization exceptions and returns null

by Tom Fennelly (JIRA)

CLONE -Base64 encode "swallows" serialization exceptions and returns null ------------------------------------------------------------------------- Key: JBESB-1280 URL: http://jira.jboss.com/jira/browse/JBESB-1280 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR2 Reporter: Tom Fennelly Fix For: 4.2.1 triage It's doing an.eprintStackTrace() and returning null, creating uncontrollable noise on the console + loosing valuable info for callers up the stack. -- 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

16 years, 8 months

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-1279) Base64 encode "swallows" serialization exceptions and returns null

by Tom Fennelly (JIRA)

Base64 encode "swallows" serialization exceptions and returns null ------------------------------------------------------------------ Key: JBESB-1279 URL: http://jira.jboss.com/jira/browse/JBESB-1279 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR2 Reporter: Tom Fennelly Fix For: 4.2.1 triage It's doing an.eprintStackTrace() and returning null, creating uncontrollable noise on the console + loosing valuable info for callers up the stack. -- 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

16 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1191) Unclear warning for unresponsive EPR

by Martin Vecera (JIRA)

Unclear warning for unresponsive EPR ------------------------------------ Key: JBESB-1191 URL: http://jira.jboss.com/jira/browse/JBESB-1191 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR2 Environment: Xen guest, Sun JVM Reporter: Martin Vecera Assigned To: Mark Little While running webservice producer performance test (see https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/performance6) I made one of my EPR to become unresponsive for a while. This test is working with only one EPR at the same time so I would expect that ESB shows me this EPR. Instead of this it showed me incorrectly all the EPRs currently configured: 15:07:54,183 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address http://0.0.0.0:8765/> > for message: header: [ To: null, From: null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ] 15:07:54,336 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address socket://0.0.0.0:8888/> > for message: header: [ To: null, From: null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ] I tried to add one more completely unused EPR to see if ESB shows really everything. Guess what - it shows: 15:23:29,141 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address http://0.0.0.0:8765/> > for message: header: [ To: null, From: null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ] 15:23:29,141 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address http://0.0.0.0:18888/> > for message: header: [ To: null, From: null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ] 15:23:29,142 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address socket://0.0.0.0:8888/> > for message: header: [ To: null, From: null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ] -- 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

16 years, 8 months

3
14
0 / 0

[JBoss JIRA] Created: (JBESB-1122) Incorporate new documentation on Notifiers into Message Action Guide / Incorporate Notifier quickstart into codebase

by Richard Achmatowicz (JIRA)

Incorporate new documentation on Notifiers into Message Action Guide / Incorporate Notifier quickstart into codebase -------------------------------------------------------------------------------------------------------------------- Key: JBESB-1122 URL: http://jira.jboss.com/jira/browse/JBESB-1122 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 IR1 Reporter: Richard Achmatowicz Assigned To: Kevin Conner Priority: Minor I have created some documentation for Notifier classes and their parameters which can be added to the MessageActionGuide under the Notifiers section, to provide users with information on what the notifiers will do and the parameters they can accept. I have also created a new quickstart which demonstarts their use. These are in JBQA-1046. Could you please incorporate this information into the current MessageACtion Guide and also update the codebase with the new quickstart (if desired). The quickstart has been tested and seems to work fine. -- 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

16 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1277) Update release notes

by Kevin Conner (JIRA)

Update release notes -------------------- Key: JBESB-1277 URL: http://jira.jboss.com/jira/browse/JBESB-1277 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 As part of this task all issues closed against IR1/IR2/triage should be moved into 4.2.1 -- 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

16 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1287) Undeploying scheduled_services results in console ERROR message

by Kevin Conner (JIRA)

Undeploying scheduled_services results in console ERROR message --------------------------------------------------------------- Key: JBESB-1287 URL: http://jira.jboss.com/jira/browse/JBESB-1287 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Fix For: 4.3 19:34:34,513 ERROR [ScheduleProvider] Failed to delete scheduled Job '3-sec-trigger-5' from job group 'JBossESB'. -- 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

16 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-1285) Mofidy wiretap jboss-esb.xml to remove warnings

by Kevin Conner (JIRA)

Mofidy wiretap jboss-esb.xml to remove warnings ----------------------------------------------- Key: JBESB-1285 URL: http://jira.jboss.com/jira/browse/JBESB-1285 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 -- 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

16 years, 8 months

1
11
0 / 0

[JBoss JIRA] Created: (JBESB-1221) load_generator QS should throw more polite compilation error

by Tom Cunningham (JIRA)

load_generator QS should throw more polite compilation error ------------------------------------------------------------ Key: JBESB-1221 URL: http://jira.jboss.com/jira/browse/JBESB-1221 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 In other QS, if we are missing dependencies we throw errors explaining what they are and saying how to fix them. We should do the same with load_generator's GROOVY dependency. drseuss:~/src/esb/trunk/product/samples/quickstarts/load_generator tcunning$ ant clean deploy Buildfile: build.xml BUILD FAILED /Users/tcunning/src/esb/trunk/product/samples/quickstarts/load_generator/build.xml:21: /Users/tcunning/src/esb/trunk/product/samples/quickstarts/load_generator/${env.GROOVY_HOME}/embeddable not found. Total time: 0 seconds -- 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

16 years, 8 months

5
11
0 / 0

[JBoss JIRA] Created: (JBESB-1216) dynamic_router quickstart exceptions

by Tom Cunningham (JIRA)

dynamic_router quickstart exceptions ------------------------------------ Key: JBESB-1216 URL: http://jira.jboss.com/jira/browse/JBESB-1216 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 After deploying the dynamic_router quickstart to a completely fresh ESB server, I followed the next step in the instructions and got this exception: % ant receive-destination1 Server shows : 15:47:56,596 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 15:48:07,943 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/C/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-4 RelatesTo: jms:correlationID#ID:JBM-512 ] 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:273) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) 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:613) Caused by: java.lang.NullPointerException at java.lang.String.<init>(String.java:479) at org.jboss.soa.esb.samples.quickstart.dynamicRouter.MyControlAction.processControlMessage(MyControlAction.java:61) 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 15:48:07,948 WARN [ActionProcessingPipeline] No fault address defined for fault message! header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/C/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-4 RelatesTo: jms:correlationID#ID:JBM-512 ] -- 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

16 years, 8 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2007