September 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2756) No quickstart for http-provider

by Aaron Pestel (JIRA)

No quickstart for http-provider ------------------------------- Key: JBESB-2756 URL: https://jira.jboss.org/jira/browse/JBESB-2756 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.6 Environment: JBoss ESB 4.6 Reporter: Aaron Pestel We need a quickstart for http-provider. I'm attaching one I got from Burr previously. It doesn't seem to work out of the box for me, but may be a good place to start. -- 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, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-2815) Negative values shows up in Overall Bytes at the action level

by Jaroslaw Kijanowski (JIRA)

Negative values shows up in Overall Bytes at the action level ------------------------------------------------------------- Key: JBESB-2815 URL: https://jira.jboss.org/jira/browse/JBESB-2815 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management, Tooling Affects Versions: 4.4 CP2 Reporter: Jaroslaw Kijanowski Assignee: Tom Cunningham -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2625) Add v1.2 XSD

by Tom Fennelly (JIRA)

Add v1.2 XSD ------------ Key: JBESB-2625 URL: https://jira.jboss.org/jira/browse/JBESB-2625 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 -- 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, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-2473) http-listener: Add security related intergration code e.g. mapping auth info onto message etc

by Tom Fennelly (JIRA)

http-listener: Add security related intergration code e.g. mapping auth info onto message etc --------------------------------------------------------------------------------------------- Key: JBESB-2473 URL: https://jira.jboss.org/jira/browse/JBESB-2473 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 FP1 At the moment, the new http-listener allows you to specify a user configured web.xml. Should also allow specification of a jboss-web.xml. -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2757) Implement a common codebase on which war based sub deployments (gateways etc) can be based

by Tom Fennelly (JIRA)

Implement a common codebase on which war based sub deployments (gateways etc) can be based ------------------------------------------------------------------------------------------ Key: JBESB-2757 URL: https://jira.jboss.org/jira/browse/JBESB-2757 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.7 This is to accommodate merging of EBWS and HttpGateway war deployment requirements in a single "per .esb" war sub deployment. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2618) Merge new http gateway across to trunk

by Kevin Conner (JIRA)

Merge new http gateway across to trunk -------------------------------------- Key: JBESB-2618 URL: https://jira.jboss.org/jira/browse/JBESB-2618 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Tom Fennelly Fix For: 4.6 Move the version in the FP release across. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2811) Quickstarts: notifications - NullPointerException after undeploying

by Boris Belovic (JIRA)

Quickstarts: notifications - NullPointerException after undeploying ------------------------------------------------------------------- Key: JBESB-2811 URL: https://jira.jboss.org/jira/browse/JBESB-2811 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Boris Belovic Priority: Minor There is NullPointerException after undeploying this quickstart. I ran the sequence (as described in readme.txt): 1. ant deploy 2. ant receive-from-queue 3. ant receive-from-topic 4. ant runtest 5. then there was an expected result from ESB 6. I stopped the processes listening on queue and topic by CTRL-C 7. ant undeploy After this I got NPE in server console: 10:59:06,756 INFO [STDOUT] ConsoleNotifier 2009/09/01 10:59:06.756<Hello from ESB-unaware JMS Client> 10:59:55,547 INFO [TopicService] Topic[/topic/quickstart_notifications_topic] stopped 10:59:55,549 INFO [QueueService] Queue[/queue/quickstart_notifications_queue] stopped 10:59:55,551 INFO [QueueService] Queue[/queue/quickstart_notifications_gw] stopped 10:59:55,553 INFO [QueueService] Queue[/queue/quickstart_notifications_esb] stopped 10:59:55,554 WARN [ServiceMessageCounterLifecycleResource] Calling cleanup on existing service message counters for identity ID-11 11:00:08,049 ERROR [ExceptionUtil] ConnectionEndpoint[d6-36jqe2zf-1-xihnb2zf-xxpxao-100j3] close [a7-iu8se2zf-1-xihnb2zf-xxpxao-100j3] java.lang.NullPointerException at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:542) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:1159) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:395) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$close$aop(ConnectionAdvised.java:63) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$close_N4742752445160157748.invokeNext(ConnectionAdvised$close_N4742752445160157748.java) at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$close_N4742752445160157748.invokeNext(ConnectionAdvised$close_N4742752445160157748.java) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.close(ConnectionAdvised.java) at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.cleanupForSessionID(SimpleConnectionManager.java:488) at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:201) at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(SimpleConnectionManager.java:241) at org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:60) at org.jboss.remoting.Lease.notifyClientLost(Lease.java:338) at org.jboss.remoting.Lease.access$600(Lease.java:40) at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:404) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2769) Upgrade groovy to 1.5.4

by Kevin Conner (JIRA)

Upgrade groovy to 1.5.4 ----------------------- Key: JBESB-2769 URL: https://jira.jboss.org/jira/browse/JBESB-2769 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Scripting Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 This brings it in line with seam/EAP 5. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2810) Quickstarts: native_client - Documentation needs update

by Boris Belovic (JIRA)

Quickstarts: native_client - Documentation needs update ------------------------------------------------------- Key: JBESB-2810 URL: https://jira.jboss.org/jira/browse/JBESB-2810 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.4 Reporter: Boris Belovic Priority: Minor There is ActionProcessingException thrown in this quickstart. This exception is thrown in MyAction.java file on line 79 and it is thrown using regular throw new ActionProcessingException(..) statement. So I guess throwing of this exception was intended by creators of this quickstart. Throwing of this exception is not mentioned in readme.txt, this document probably needs to be updated. The readme.txt document also mentions that after hitting http://localhost:8080/jbossws we should see something like this: ------------------------------------------------------------------------------------------------ | jboss.ws:context=Quickstart_native_client,endpoint=HelloWorldWS | | http://127.0.0.1:8080/Quickstart_native_client/HelloWorldWS?wsdl | ------------------------------------------------------------------------------------------------ but http://localhost:8080/jbossws points to JBoss Web Services Main page, the list of deployed webservices can be found on http://localhost:8080/jbossws/services. -- 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, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2009