[JBoss JIRA] (JBESB-3747) remove-old-service will throw ServiceNotFoundException, skip registerEpr
by Tom Cunningham (JIRA)
Tom Cunningham created JBESB-3747:
-------------------------------------
Summary: remove-old-service will throw ServiceNotFoundException, skip registerEpr
Key: JBESB-3747
URL: https://issues.jboss.org/browse/JBESB-3747
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.11
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.11
>From Martin Weiler:
In case the service is being deployed for the first time, this
setting prevents it from being registered:
try
{
if ("true".equalsIgnoreCase(removeOldService))
registry.unRegisterService(category, name);
registry.registerEPR(category, name,
serviceDescription, epr, eprDescription) ;
}
catch (ServiceNotFoundException ex)
{
// ignore as it's possible another client just did
the removal for us.
logger.debug("Could not unregister service<
"+category+", "+name+">.");
}
Shouldn't the registry.registerEPR call happen after the
ServiceNotFoundException is caught?
--
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
12 years, 2 months
[JBoss JIRA] (JBESB-3749) MessageFilter QuickStart fails deploying to ESB Server
by Sandeep R (JIRA)
Sandeep R created JBESB-3749:
--------------------------------
Summary: MessageFilter QuickStart fails deploying to ESB Server
Key: JBESB-3749
URL: https://issues.jboss.org/browse/JBESB-3749
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Sandeep R
Hi,
I am getting below error while deploying ESB
org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Error configuring action processing pipeline
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:191)
at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133)
at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:109)
at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:66)
at org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment.start(EsbDeployment.java:125)
at sun.reflect.GeneratedMethodAccessor361.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
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)
--
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
12 years, 2 months
[JBoss JIRA] (JBESB-3733) Incorrect host used in ESB binding service
by Tom Cunningham (JIRA)
Tom Cunningham created JBESB-3733:
-------------------------------------
Summary: Incorrect host used in ESB binding service
Key: JBESB-3733
URL: https://issues.jboss.org/browse/JBESB-3733
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 4.11
Reporter: Tom Cunningham
Fix For: 4.11
The binding information for the ESB services refers to jboss.bind.address as the value of esbHost rather than jboss.esb.bind.address.
The difference between the two is evident when the server is started with the -b 0.0.0.0 option, i.e. binding to any interface, as the value of the processed esb.juddi.properties and jbossesb-properties.xml will contain 0.0.0.0 for juddi.server.baseurl and
org.jboss.soa.esb.jndi.server.url respectively.
The ESB should be using an explicit interface which is what the jboss.esb.bind.address represents.
--
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
12 years, 2 months
[JBoss JIRA] Created: (JBESB-3688) Juddi errors on redeploy of ESB components in 4.10
by Sven-Jørgen Karlsen (JIRA)
Juddi errors on redeploy of ESB components in 4.10
---------------------------------------------------
Key: JBESB-3688
URL: https://issues.jboss.org/browse/JBESB-3688
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 4.10
Environment: Ubuntu Linux 10.x, MS Windows 7
Reporter: Sven-Jørgen Karlsen
The symptoms are:
...
13:54:42,985 ERROR [RequestHandler] obj+parameter+must+not+be+null
13:54:43,031 ERROR [RequestHandler] The+binding+template+was+not+found+for+the+given+key%3A++uddi%3Ajuddi.apache.org%3Ace12edd3-12d1-42c7-b425-7651fe4b2192
...
in the server log on redeployments of most ESB components. Even jbossesb.esb itself.
It also occurs on 6.1.0.Final, and on both a clustered and non-clustered configuration.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months