[JBoss JIRA] Created: (JBESB-500) package rules, jbpm and smooks as services
by Kurt Stam (JIRA)
package rules, jbpm and smooks as services
------------------------------------------
Key: JBESB-500
URL: http://jira.jboss.com/jira/browse/JBESB-500
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Kurt Stam
Assigned To: Kurt Stam
Fix For: 4.2 Milestone Release 2
If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories:
services/jbpm -> jbpm.esb
services/smooks -> smooks.esb
services/cbr/jbr -> cbr-jbr.esb
each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.
--
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
17 years
[JBoss JIRA] Created: (JBESB-479) deploying queues in esb archive does not work in scoped JBM deployments
by Kurt Stam (JIRA)
deploying queues in esb archive does not work in scoped JBM deployments
-----------------------------------------------------------------------
Key: JBESB-479
URL: http://jira.jboss.com/jira/browse/JBESB-479
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBossAS4.0.5 with JBM in a scoped sar.
Reporter: Kurt Stam
Assigned To: Mark Little
When deploying a queue-service.xml (with or without) scoping information on JBM in a scoped sar (Needed in the full JBossAS environment) the deployment fails, see the stacktrace below.
Note that this works fine in the standalone jbossesb-server where JBM is deployed in an Unscoped sar.
2007-03-20 09:29:40,953 DEBUG [org.jboss.system.ServiceController] starting service jboss.messaging.destination:service=Queue,name=quickstart_helloworld_Request
2007-03-20 09:29:40,953 DEBUG [org.jboss.jms.server.destination.QueueService] Starting jboss.messaging.destination:service=Queue,name=quickstart_helloworld_Request
2007-03-20 09:29:40,953 ERROR [org.jboss.jms.util.ExceptionUtil] Queue[(destination.getName() == NULL)] startService
java.lang.ClassCastException: org.jboss.jms.server.ServerPeer
at org.jboss.jms.server.destination.DestinationServiceSupport.startService(DestinationServiceSupport.java:107)
at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:63)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
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(ServiceController.java:995)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
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 $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
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 $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:595)
2007-03-20 09:29:41,000 DEBUG [org.jboss.jms.server.destination.QueueService] Starting failed jboss.messaging.destination:service=Queue,name=quickstart_helloworld_Request
java.lang.ClassCastException: org.jboss.jms.server.ServerPeer
at org.jboss.jms.server.destination.DestinationServiceSupport.startService(DestinationServiceSupport.java:107)
at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:63)
--
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
17 years
[JBoss JIRA] Created: (JBESB-519) Update quickstarts to more clearly demonstrate deployToAS vs deployToESB
by Burr Sutter (JIRA)
Update quickstarts to more clearly demonstrate deployToAS vs deployToESB
------------------------------------------------------------------------
Key: JBESB-519
URL: http://jira.jboss.com/jira/browse/JBESB-519
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Fix For: 4.2 Milestone Release 2
Based on the introduction of the ESB Server in 4.2 MR1 the quickstarts are a little bit confusing. Helloworld base-build.xml refers to "JBoss ESB Server at '${jbosshome.dir}'." when jbosshome.dir should be mapped to the AS, not to the ESB home.
I propose that quickstart.properties have a AS home and ESB home and the build.xml's updated accordingly. As it stands not the jbosshome.dir is being overloaded.
The helloworld quickstart (and ideally all of them) should illustrate:
- StandAloneBootStrapper
- AS deployment (previously known as SAR deployment)
- ESB server deployment (new in 4.2)
- WAR deployment (if that model actually works)
Not every quickstart works with the ESB server and I believe this needs to be more clearly specified in the readme.txt
--
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
17 years
[JBoss JIRA] Created: (JBESB-518) Exception logging
by Kevin Conner (JIRA)
Exception logging
-----------------
Key: JBESB-518
URL: http://jira.jboss.com/jira/browse/JBESB-518
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.2 Milestone Release 1
Reporter: Kevin Conner
Assigned To: Mark Little
There are numerous locations in the code where exceptions are being logged at a high logging level. Some of these include locations where the exceptions are being rethrown or ignored.
It would be better if these exceptions were logged at DEBUG level and, if neccessary, accompanied with an appropriate logging message at a higher level.
--
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
17 years
[JBoss JIRA] Created: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
by Burr Sutter (JIRA)
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with unique services. A single message flow could be routed throughout all the different ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that conflict with other running ESB Servers. You can now basically only run a single ESB Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI complains (upon ESB Server boot up).
More details in the comments
--
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
17 years, 2 months