[JBoss JIRA] (DROOLS-336) Property Reactivity fails on phreak
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-336?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-336.
--------------------------------
Fix Version/s: 6.0.1.Final
Resolution: Done
> Property Reactivity fails on phreak
> -----------------------------------
>
> Key: DROOLS-336
> URL: https://issues.jboss.org/browse/DROOLS-336
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.0.1.Final
>
>
> In LeftInputAdapterNode a modifyByPass happens, for a sink that has not been reached before. So it thinks it's new, and thus propagates as an insert
> The real bug comes in doInsertObject method. It creates a child LT here, even though once it enters doInsertSegmentMemory the mask intersect fails. This leaves a child LT, that is not propagated. Next time update is called, as the LT is there it thinks it's a modify and propagates as a modify - but it never reached the beta node or the LeftMemory, and thus the memory corruption.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBAS-9552) java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
by Sergey Smirnov (JIRA)
[ https://issues.jboss.org/browse/JBAS-9552?page=com.atlassian.jira.plugin.... ]
Sergey Smirnov updated JBAS-9552:
---------------------------------
Description:
I work with Documentum platform, can any one adnise me with next proplem:
First loaded from this part :
[Loaded javax.xml.namespace.QName from /u01/documentum/ord/shared/jboss5.1.0/lib/endorsed/stax-api.jar]
and then
[Loaded javax.xml.namespace.QName from jar:file:/u01/documentum/ord/shared/jboss5.1.0/server/DctmServer_MethodServer/deploy/bpm.ear/bpm.war/WEB-INF/lib/sibc.jms.jar!/]
18:25:09,251 INFO [STDOUT] 2013-11-12 18:25:09,250 ERROR [http-0.0.0.0-9080-49] [ru.atconsulting.dms.methods.workflow.integration.contractex.event.ATCWFExecuteEvent] - loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName" .....................
java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
at oracle.apps.xxrt.xxcn348.contract.service.ContractServicePortBindingStub._initOperationDesc1(ContractServicePortBindingStub.java:30)
at oracle.apps.xxrt.xxcn348.contract.service.ContractServicePortBindingStub.<clinit>(ContractServicePortBindingStub.java:20)
at ru.atconsulting.esed.services.integration.contractex.dctm2oebs.common.AbstractWSClientContractEx.perform(AbstractWSClientContractEx.java:163)
at ru.company.dms.methods.workflow.integration.contractex.event.requests.impl.ConfirmContractCreateImpl.exec(ConfirmContractCreateImpl.java:47)
at ru.company.dms.methods.workflow.integration.contractex.event.requests.impl.AbstractForwardRequest.forward(AbstractForwardRequest.java:127)
at ru.company.dms.methods.workflow.integration.contractex.event.ATCWFExecuteEvent.doTask(ATCWFExecuteEvent.java:128)
at com.documentum.bpm.rtutil.WorkflowMethod.execute(WorkflowMethod.java:214)
at com.documentum.bpm.rtutil.AbstractWorkflowMethod.executeMethod(AbstractWorkflowMethod.java:27)
at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:124)
at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:65)
at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)
at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)
at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)
at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:662)
After analyze app server i found :
Like this:
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\jaxrpc.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\sibc.jms.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\qname.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\lib\endorsed\stax-api.jar\javax\xml\namespace\QName.class
as a result, I get the error in my custom module :
java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
How can I fixed that?
was:
First loaded from this part :
[Loaded javax.xml.namespace.QName from /u01/documentum/ord/shared/jboss5.1.0/lib/endorsed/stax-api.jar]
and then
[Loaded javax.xml.namespace.QName from jar:file:/u01/documentum/ord/shared/jboss5.1.0/server/DctmServer_MethodServer/deploy/bpm.ear/bpm.war/WEB-INF/lib/sibc.jms.jar!/]
18:25:09,251 INFO [STDOUT] 2013-11-12 18:25:09,250 ERROR [http-0.0.0.0-9080-49] [ru.atconsulting.dms.methods.workflow.integration.contractex.event.ATCWFExecuteEvent] - loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName" .....................
java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
at oracle.apps.xxrt.xxcn348.contract.service.ContractServicePortBindingStub._initOperationDesc1(ContractServicePortBindingStub.java:30)
at oracle.apps.xxrt.xxcn348.contract.service.ContractServicePortBindingStub.<clinit>(ContractServicePortBindingStub.java:20)
at ru.atconsulting.esed.services.integration.contractex.dctm2oebs.common.AbstractWSClientContractEx.perform(AbstractWSClientContractEx.java:163)
at ru.company.dms.methods.workflow.integration.contractex.event.requests.impl.ConfirmContractCreateImpl.exec(ConfirmContractCreateImpl.java:47)
at ru.company.dms.methods.workflow.integration.contractex.event.requests.impl.AbstractForwardRequest.forward(AbstractForwardRequest.java:127)
at ru.company.dms.methods.workflow.integration.contractex.event.ATCWFExecuteEvent.doTask(ATCWFExecuteEvent.java:128)
at com.documentum.bpm.rtutil.WorkflowMethod.execute(WorkflowMethod.java:214)
at com.documentum.bpm.rtutil.AbstractWorkflowMethod.executeMethod(AbstractWorkflowMethod.java:27)
at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:124)
at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:65)
at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)
at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)
at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)
at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:662)
After analyze app server i found :
Like this:
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\jaxrpc.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\sibc.jms.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\qname.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\lib\endorsed\stax-api.jar\javax\xml\namespace\QName.class
as a result, I get the error in my custom module :
java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
How can I fixed that?
> java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-9552
> URL: https://issues.jboss.org/browse/JBAS-9552
> Project: Application Server 3 4 5 and 6
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ClassLoading
> Affects Versions: JBossAS-5.1.0.GA
> Reporter: Sergey Smirnov
> Assignee: Ales Justin
> Labels: jboss, worked
>
> I work with Documentum platform, can any one adnise me with next proplem:
> First loaded from this part :
> [Loaded javax.xml.namespace.QName from /u01/documentum/ord/shared/jboss5.1.0/lib/endorsed/stax-api.jar]
> and then
> [Loaded javax.xml.namespace.QName from jar:file:/u01/documentum/ord/shared/jboss5.1.0/server/DctmServer_MethodServer/deploy/bpm.ear/bpm.war/WEB-INF/lib/sibc.jms.jar!/]
> 18:25:09,251 INFO [STDOUT] 2013-11-12 18:25:09,250 ERROR [http-0.0.0.0-9080-49] [ru.atconsulting.dms.methods.workflow.integration.contractex.event.ATCWFExecuteEvent] - loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName" .....................
> java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
> at oracle.apps.xxrt.xxcn348.contract.service.ContractServicePortBindingStub._initOperationDesc1(ContractServicePortBindingStub.java:30)
> at oracle.apps.xxrt.xxcn348.contract.service.ContractServicePortBindingStub.<clinit>(ContractServicePortBindingStub.java:20)
> at ru.atconsulting.esed.services.integration.contractex.dctm2oebs.common.AbstractWSClientContractEx.perform(AbstractWSClientContractEx.java:163)
> at ru.company.dms.methods.workflow.integration.contractex.event.requests.impl.ConfirmContractCreateImpl.exec(ConfirmContractCreateImpl.java:47)
> at ru.company.dms.methods.workflow.integration.contractex.event.requests.impl.AbstractForwardRequest.forward(AbstractForwardRequest.java:127)
> at ru.company.dms.methods.workflow.integration.contractex.event.ATCWFExecuteEvent.doTask(ATCWFExecuteEvent.java:128)
> at com.documentum.bpm.rtutil.WorkflowMethod.execute(WorkflowMethod.java:214)
> at com.documentum.bpm.rtutil.AbstractWorkflowMethod.executeMethod(AbstractWorkflowMethod.java:27)
> at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:124)
> at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:65)
> at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)
> at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)
> at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)
> at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:662)
> After analyze app server i found :
> Like this:
> $DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\jaxrpc.jar\javax\xml\namespace\QName.class
> $DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\sibc.jms.jar\javax\xml\namespace\QName.class
> $DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\qname.jar\javax\xml\namespace\QName.class
> $DOCUMENTUM_SHARED\jboss5.1.0\lib\endorsed\stax-api.jar\javax\xml\namespace\QName.class
>
> as a result, I get the error in my custom module :
> java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
> How can I fixed that?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBAS-9552) java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
by Sergey Smirnov (JIRA)
Sergey Smirnov created JBAS-9552:
------------------------------------
Summary: java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
Key: JBAS-9552
URL: https://issues.jboss.org/browse/JBAS-9552
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-5.1.0.GA
Reporter: Sergey Smirnov
Assignee: Ales Justin
First loaded from this part :
[Loaded javax.xml.namespace.QName from /u01/documentum/ord/shared/jboss5.1.0/lib/endorsed/stax-api.jar]
and then
[Loaded javax.xml.namespace.QName from jar:file:/u01/documentum/ord/shared/jboss5.1.0/server/DctmServer_MethodServer/deploy/bpm.ear/bpm.war/WEB-INF/lib/sibc.jms.jar!/]
18:25:09,251 INFO [STDOUT] 2013-11-12 18:25:09,250 ERROR [http-0.0.0.0-9080-49] [ru.atconsulting.dms.methods.workflow.integration.contractex.event.ATCWFExecuteEvent] - loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName" .....................
java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
at oracle.apps.xxrt.xxcn348.contract.service.ContractServicePortBindingStub._initOperationDesc1(ContractServicePortBindingStub.java:30)
at oracle.apps.xxrt.xxcn348.contract.service.ContractServicePortBindingStub.<clinit>(ContractServicePortBindingStub.java:20)
at ru.atconsulting.esed.services.integration.contractex.dctm2oebs.common.AbstractWSClientContractEx.perform(AbstractWSClientContractEx.java:163)
at ru.company.dms.methods.workflow.integration.contractex.event.requests.impl.ConfirmContractCreateImpl.exec(ConfirmContractCreateImpl.java:47)
at ru.company.dms.methods.workflow.integration.contractex.event.requests.impl.AbstractForwardRequest.forward(AbstractForwardRequest.java:127)
at ru.company.dms.methods.workflow.integration.contractex.event.ATCWFExecuteEvent.doTask(ATCWFExecuteEvent.java:128)
at com.documentum.bpm.rtutil.WorkflowMethod.execute(WorkflowMethod.java:214)
at com.documentum.bpm.rtutil.AbstractWorkflowMethod.executeMethod(AbstractWorkflowMethod.java:27)
at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:124)
at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:65)
at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)
at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)
at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)
at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:662)
After analyze app server i found :
Like this:
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\jaxrpc.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\sibc.jms.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB-INF\lib\qname.jar\javax\xml\namespace\QName.class
$DOCUMENTUM_SHARED\jboss5.1.0\lib\endorsed\stax-api.jar\javax\xml\namespace\QName.class
as a result, I get the error in my custom module :
java.lang.LinkageError: loader constraint violation: loader (instance of com/documentum/fc/client/impl/bof/classmgmt/URLClassLoaderEx) previously initiated loading for a different type with name "javax/xml/namespace/QName"
How can I fixed that?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-2160) Allow Expression for datasource subsystem enabled property
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2160?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-2160:
---------------------------------
Assignee: Stefano Maestri (was: Tomaz Cerar)
> Allow Expression for datasource subsystem enabled property
> ----------------------------------------------------------
>
> Key: WFLY-2160
> URL: https://issues.jboss.org/browse/WFLY-2160
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management, JCA
> Affects Versions: 8.0.0.Alpha4
> Reporter: Steven Rose
> Assignee: Stefano Maestri
> Priority: Minor
> Labels: wildfly
> Fix For: 8.0.0.CR1
>
>
> Currently the datasource sub system does not allow expressions. I would like to be able to do this: <datasource jta="true" jndi-name="java:/ds1DS" pool-name="ds1DS" enabled="${ds1.enabled}" use-java-context="true" use-ccm="true"> and set the ds1.enabled property via a properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-1773) NPE in Host.unregisterDeployment
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1773?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-1773:
-----------------------------------
Is it any different with latest builds?
> NPE in Host.unregisterDeployment
> --------------------------------
>
> Key: WFLY-1773
> URL: https://issues.jboss.org/browse/WFLY-1773
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Thomas Diesler
> Assignee: Tomaz Cerar
>
> {code}
> 15:37:13,687 INFO [org.jboss.osgi.framework] (pool-1-thread-3) JBOSGI011003: Bundle stopped: bundle-c.wab:0.0.0
> 15:37:13,689 WARN [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000004: Failure during stop of service jboss.undertow.deployment.default-host./bundle-c: java.lang.NullPointerException
> at org.wildfly.extension.undertow.Host.unregisterDeployment(Host.java:130)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:104)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2052) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-1018) Improve error reporting on misconfigured security-realm
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1018?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-1018:
-----------------------------------
does this still happen?
> Improve error reporting on misconfigured security-realm
> -------------------------------------------------------
>
> Key: WFLY-1018
> URL: https://issues.jboss.org/browse/WFLY-1018
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Alessio Soldano
> Assignee: Tomaz Cerar
> Priority: Minor
>
> I've erroneously configured standalone.xml with an empty (no child) security realm and referenced it in a undertow https listenerer.
> When running a test relying on https, I'm getting the following error only on server side:
> 11:43:44,482 ERROR [org.xnio.listener] (default I/O-3) A channel event listener threw an exception: java.lang.NullPointerException
> at org.xnio.ssl.AbstractAcceptingSslChannel.accept(AbstractAcceptingSslChannel.java:143) [xnio-api-3.1.0.CR2.jar:3.1.0.CR2]
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:288) [xnio-api-3.1.0.CR2.jar:3.1.0.CR2]
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:285) [xnio-api-3.1.0.CR2.jar:3.1.0.CR2]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.CR2.jar:3.1.0.CR2]
> at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1052) [xnio-api-3.1.0.CR2.jar:3.1.0.CR2]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.CR2.jar:3.1.0.CR2]
> at org.xnio.nio.NioTcpServerHandle.handleReady(NioTcpServerHandle.java:53) [xnio-nio-3.1.0.CR2.jar:3.1.0.CR2]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:528) [xnio-nio-3.1.0.CR2.jar:3.1.0.CR2]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-2458) Re-deployment of a clustered application fail due to race-condition with infinispan
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2458?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2458:
-----------------------------------------------
Ladislav Thon <lthon(a)redhat.com> made a comment on [bug 1027738|https://bugzilla.redhat.com/show_bug.cgi?id=1027738]
I built the current EAP "upstream" branch which has the fix, and I can confirm that the issue is indeed fixed. Please take this as a preliminary feedback; once we get official build, we will provide official QA statement.
> Re-deployment of a clustered application fail due to race-condition with infinispan
> -----------------------------------------------------------------------------------
>
> Key: WFLY-2458
> URL: https://issues.jboss.org/browse/WFLY-2458
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering, Server
> Affects Versions: 8.0.0.Beta1
> Environment: Clustered Standalone server with one clustered EAR
> Reporter: Wolf-Dieter Fink
> Assignee: Paul Ferraro
> Labels: deployer
> Fix For: 8.0.0.CR1
>
> Attachments: appone.ear
>
>
> If a clustered application should be redeployed it looks like that infinispan is not able to stop complete until the deployer finish undeployment and start to deploy the new application. See the Exception below.
> The behaviour is the same for managed or unmanged deployments.
> If it is unmanaged the .failed marker file exists.
> After the failure the application is shown in the mgmt console without deployed Beans.
> A second deploy attempt will be successfull
> 11:22:36,397 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,shared=udp) ISPN000094: Received new cluster view: [home/ejb|1] (2) [home/ejb, node2/ejb]
> 11:22:52,746 INFO [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016009: Stopping weld service for deployment appone.ear
> 11:22:52,751 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 58) ISPN000029: Passivating all entries to disk
> 11:22:52,752 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 58) ISPN000030: Passivated 0 entries in 0 milliseconds
> 11:22:52,759 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58) JBAS010282: Stopped repl cache from ejb container
> 11:22:52,765 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 60) JBAS010282: Stopped remote-connector-client-mappings cache from ejb container
> 11:22:52,768 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting and closing JGroups Channel
> 11:22:52,771 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment null (runtime-name: ejb.jar) in 36ms
> 11:22:52,772 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment appone.ear (runtime-name: appone.ear) in 39ms
> 11:22:52,773 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "appone.ear" (runtime-name: "appone.ear")
> 11:22:52,778 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "null" (runtime-name: "ejb.jar")
> 11:22:52,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) JBAS016002: Processing weld deployment appone.ear
> 11:22:52,803 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016002: Processing weld deployment ejb.jar
> 11:22:52,805 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named AppOneBean in deployment unit subdeployment "ejb.jar" of deployment "appone.ear" are as follows:
> java:global/appone/ejb/AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne
> java:app/ejb/AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne
> java:module/AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne
> java:jboss/exported/appone/ejb/AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne
> java:global/appone/ejb/AppOneBean
> java:app/ejb/AppOneBean
> java:module/AppOneBean
> 11:22:52,807 INFO [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016005: Starting Services for CDI deployment: appone.ear
> 11:22:52,811 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment appone.ear
> 11:22:53,087 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher
> 11:22:53,118 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 60) ISPN000078: Starting JGroups Channel
> 11:22:53,119 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 60) MSC000001: Failed to start service jboss.infinispan.ejb.global-component-registry: org.jboss.msc.service.StartException in service jboss.infinispan.ejb.global-component-registry: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object of type JGroupsTransport
> at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:91) [wildfly-clustering-common-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
> Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object of type JGroupsTransport
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:241)
> at org.jboss.as.clustering.infinispan.subsystem.GlobalComponentRegistryService.start(GlobalComponentRegistryService.java:33)
> at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:86) [wildfly-clustering-common-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]
> ... 4 more
> Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object of type JGroupsTransport
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:185)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530)
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:219)
> ... 6 more
> Caused by: org.infinispan.commons.CacheException: Unable to start JGroups Channel
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:196)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:185)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:183)
> ... 11 more
> Caused by: java.lang.IllegalStateException: channel is closed
> at org.jgroups.JChannel.checkClosed(JChannel.java:902)
> at org.jgroups.JChannel._preConnect(JChannel.java:522)
> at org.jgroups.JChannel.connect(JChannel.java:284)
> at org.jgroups.JChannel.connect(JChannel.java:275)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:194)
> ... 17 more
> 11:22:53,128 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016009: Stopping weld service for deployment appone.ear
> 11:22:53,137 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment null (runtime-name: ejb.jar) in 11ms
> 11:22:53,138 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment appone.ear (runtime-name: appone.ear) in 12ms
> 11:22:53,143 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.CREATE (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".moduleDeploymentRuntimeInformation, service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START, service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.VIEW."org.jboss.as.quickstarts.ejb.multi.server.app.AppOne".REMOTE]
> service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".jndiDependencyService]
> service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".deploymentCompleteService, service jboss.deployment.subunit."appone.ear"."ejb.jar".moduleDeploymentRuntimeInformationStart]
> service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.VIEW."org.jboss.as.quickstarts.ejb.multi.server.app.AppOne".REMOTE (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".moduleDeploymentRuntimeInformation, service jboss.naming.context.java.module.appone.ejb."AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne", service jboss.naming.context.java.global.appone.ejb.AppOneBean, service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START, JBAS014799: ... and 5 more ]
> service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.WeldInstantiator (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START]
> service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START]
> service jboss.deployment.subunit."appone.ear"."ejb.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."appone.ear".deploymentCompleteService]
> service jboss.deployment.subunit."appone.ear"."ejb.jar".jndiDependencyService (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START]
> service jboss.deployment.subunit."appone.ear"."ejb.jar".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START, service jboss.deployment.subunit."appone.ear"."ejb.jar".moduleDeploymentRuntimeInformationStart]
> service jboss.naming.context.java.app.appone.ejb.AppOneBean (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.app.appone.ejb."AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne" (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.BeanManager (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".jndiDependencyService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.DefaultContextService (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.DefaultDataSource (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.DefaultManagedExecutorService (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.DefaultManagedScheduledExecutorService (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.DefaultManagedThreadFactory (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.EJBContext (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.TimerService (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.TransactionSynchronizationRegistry (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".jndiDependencyService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.UserTransaction (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".jndiDependencyService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.env (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.comp.appone.ejb.AppOneBean.env."org.jboss.as.quickstarts.ejb.multi.server.app.AppOneBean".context (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService, service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.START]
> service jboss.naming.context.java.global.appone.ejb.AppOneBean (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.global.appone.ejb."AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne" (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.module.appone.ejb.AppOneBean (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.module.appone.ejb."AppOneBean!org.jboss.as.quickstarts.ejb.multi.server.app.AppOne" (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".component.AppOneBean.JndiBindingsService]
> service jboss.naming.context.java.module.appone.ejb.BeanManager (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".jndiDependencyService]
> service jboss.naming.context.java.module.appone.ejb.env (missing) dependents: [service jboss.deployment.subunit."appone.ear"."ejb.jar".jndiDependencyService]
> JBAS014777: Services which failed to start: service jboss.infinispan.ejb.global-component-registry
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-1982) NPE in ModelControllerLock
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1982?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1982:
-----------------------------------------------
Ladislav Thon <lthon(a)redhat.com> made a comment on [bug 1024862|https://bugzilla.redhat.com/show_bug.cgi?id=1024862]
I built the current EAP "upstream" branch which has the fix, and I can confirm that the issue is indeed fixed. Please take this as a preliminary feedback; once we get official build, we will provide official QA statement.
> NPE in ModelControllerLock
> --------------------------
>
> Key: WFLY-1982
> URL: https://issues.jboss.org/browse/WFLY-1982
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Emanuel Muckenhuber
> Fix For: 8.0.0.CR1
>
>
> Just noticed this in the host-controller.log while looking into a non-progressing RespawnTestCase:
> 22:23:50,552 ERROR [org.jboss.as.controller.management-operation] (proxy-threads - 1) JBAS014612: Operation ("register-server") failed - address: ([]): java.lang.NullPointerException
> at org.jboss.as.controller.ModelControllerLock$Sync.tryAcquire(ModelControllerLock.java:75) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1220) [rt.jar:1.7.0_15]
> at org.jboss.as.controller.ModelControllerLock.lockInterruptibly(ModelControllerLock.java:48) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.acquireLock(ModelControllerImpl.java:582) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.OperationContextImpl.takeWriteLock(OperationContextImpl.java:403) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.OperationContextImpl.acquireControllerLock(OperationContextImpl.java:700) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.host.controller.mgmt.ServerToHostProtocolHandler$ServerReconnectRequestHandler$1$1.execute(ServerToHostProtocolHandler.java:268)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:610) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:488) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:257) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService.internalExecute(AbstractControllerService.java:292) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService.access$600(DomainModelControllerService.java:148)
> at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor.execute(DomainModelControllerService.java:899)
> at org.jboss.as.host.controller.mgmt.ServerToHostProtocolHandler$ServerReconnectRequestHandler$1.execute(ServerToHostProtocolHandler.java:282)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [wildfly-protocol-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [wildfly-protocol-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-2427) Launcher API
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/WFLY-2427?page=com.atlassian.jira.plugin.... ]
Ondrej Zizka edited comment on WFLY-2427 at 11/12/13 10:37 PM:
---------------------------------------------------------------
Ok I've gone through the use cases in JBDS, Arquillian and WindRide and put some API together inspired by that, let's discuss. I'll get in touch during Wednesday.
was (Author: ozizka):
Ok I've gone through the use cases in JBDS and put some API together inspired by that, let's discuss. I'll get in touch during Wednesday.
> Launcher API
> ------------
>
> Key: WFLY-2427
> URL: https://issues.jboss.org/browse/WFLY-2427
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Reporter: Brian Stansberry
> Assignee: Rob Stryker
>
> 1) The AS should have some sort of API for launching our processes so tools that want a process have a clear contract instead of having to guess at what's relevant in our ever-changing scripts.
> 2) We want the main class in our process launch to be what's invoked by java -jar jboss-modules.jar. We don't want java -jar jboss-as-launcher.jar which does some stuff and then calls org.jboss.modules.Main.
> 3) JBoss Modules itself shouldn't have a lot of the stuff in it that's relevant to an AS launcher API, because many of those things are not relevant to JBoss Modules in a generic sense.
> What we could do though is provide a launcher lib that isn't involved at all in our normal boot. Something that would only be used by tools that want to launch a separate, i.e. non-embedded, AS process.
> So, some sort of stable configuration API and then a simple
> java.lang.Process launch()
> Basically, a utility that does the ProcessBuilder stuff that everybody is doing themselves now.
> h2. HOWEVER...
> Eclipse-based tools like JBDS use Eclipse APIs for launch and would not use the above launch() method.
> So, besides that launch method, look into adding some methods to give the necessary inputs to the Eclipse API be useful. So Eclipse-based tools don't ask it for the process but can still get a standard launch configuration.
> I'd only want to do that if those methods would return something generally understandable, but a String or List<String> for classpath, List<String>s for vm/program args, some representation that "-jar jboss-modules.jar" is the way to get the main class -- those all seem generic enough.
> Any "which VM" stuff is consider out of scope; choosing the VM is the responsibility of the tool. Options that are not universally supported across VMs and are those a function of VM choice, like whether to use -server, are also out of scope.
> h2. Example of EAP 6.0 launch:
> VM arguments:
> -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/Users/max/products/runtimes/jboss-eap-6.0/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/max/products/runtimes/jboss-eap-6.0/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/max/products/runtimes/jboss-eap-6.0"
> Program argument:
> -mp "/Users/max/products/runtimes/jboss-eap-6.0/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months