Hi Romain!
I‘m still not able to build and share a simple example.
But further investigations on the topic shows that the exceptions always occur
for the second and third webapp – the later started webapps (forth and fifth)
did not “produce” any exception.
Also it does not depend on the webapp started as second or third one.
In our case:
The second webapp always “produces”:
javax.naming.NameAlreadyBoundException: ParsedName{path=QueryEngineImpl,
component=QueryEngineImpl}
javax.naming.NameAlreadyBoundException: ParsedName{path=AgentRegistry,
component=AgentRegistry}
javax.naming.NameAlreadyBoundException:
ParsedName{path=OptimisticLockingImpl!com.opentext.ecm.bpm.locking.IOptimisticLocking,
component=OptimisticLockingImpl!com.opentext.ecm.bpm.locking.IOptimisticLocking}
javax.naming.NameAlreadyBoundException:
ParsedName{path=StartStep!com.opentext.ecm.bpm.engine.step.IStepType,
component=StartStep!com.opentext.ecm.bpm.engine.step.IStepType}
javax.naming.NameAlreadyBoundException:
ParsedName{path=MetricsBean!com.opentext.ecm.bpm.miner.metrics.IMetricsBean,
component=MetricsBean!com.opentext.ecm.bpm.miner.metrics.IMetricsBean}
The third webapp always “produces”:
javax.naming.NameAlreadyBoundException: ParsedName{path=MilestoneStep,
component=MilestoneStep}
javax.naming.NameAlreadyBoundException:
ParsedName{path=NormalStep!com.opentext.ecm.bpm.engine.step.IStepType,
component=NormalStep!com.opentext.ecm.bpm.engine.step.IStepType}
javax.naming.NameAlreadyBoundException: ParsedName{path=RulesManagerFactory,
component=RulesManagerFactory}
javax.naming.NameAlreadyBoundException:
ParsedName{path=JoinStep!com.opentext.ecm.bpm.engine.step.IStepType,
component=JoinStep!com.opentext.ecm.bpm.engine.step.IStepType}
javax.naming.NameAlreadyBoundException: ParsedName{path=MetricsBean,
component=MetricsBean}
Do you have an idea what I can check to identify the cause?
Can you say if the exceptions “produced” by a webapp are connected or
independent?
Best regards,
Thomas
Von: Romain Manni-Bucau [via OpenEJB]
[mailto:[email protected]]
Gesendet: Dienstag, 3. September 2013 10:06
An: Thomas Schuler
Betreff: Re: AW: NameAlreadyBoundException while startup
That said you still cant reproduce the issue in a shareable sample?
If i have one i hope to be able to look tonight or tomorrow morning
Le 3 sept. 2013 09:56, "tschuler" <[hidden
email]</user/SendEmail.jtp?type=node&node=4664967&i=0>> a écrit :
> Hi Romain!
>
> If only one webapp is deployed, the exception is not shown. It doesn't
> matter which webapp is used.
> As soon as at least two webapps are deployed, the exception occurs. It
> doesn't matter which webapps are included and start order of the webapps
> also has no influence.
>
> Best regards,
> Thomas
>
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/NameAlreadyBoundException-while-startup-tp4664938p4664966.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
________________________________
If you reply to this email, your message will be added to the discussion below:
http://openejb.979440.n4.nabble.com/NameAlreadyBoundException-while-startup-tp4664938p4664967.html
To unsubscribe from NameAlreadyBoundException while startup, click
here<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4664938&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NjQ5Mzh8LTE4NTIyNTQ0OTI=>.
NAML<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context:
http://openejb.979440.n4.nabble.com/NameAlreadyBoundException-while-startup-tp4664938p4664971.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
