[JBoss Microcontainer Users] - Re: Struggling with jboss-classloading.xml
by ad-rocha
Hi Ales,
Thanks for your help, I just sow your answer. I followEd your instructions, but I could not deploy my RAR (all jars of my RAR reside in root dir).
Stack trace is shown below.
Andre
| 2009-11-23 09:49:23,660 WARN [org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder] (main) Error populating deployment vfszip:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar/
| org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=lib suffixes=.jar} from rysys-cobol-connector-1.1.5.rar
| at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
| at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)
| at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:141)
| at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:92)
| at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)
| at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)
| at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)
| at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
| at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
| at org.jboss.Main.boot(Main.java:221)
| at org.jboss.Main$1.run(Main.java:556)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: java.io.IOException: Child not found lib for DelegatingHandler(a)16662014[path=rysys-cobol-connector-1.1.5.rar context=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Java/jboss-5.1.0.GA/server/default/deploy/rysys-cobol-connector-1.1.5.rar], available children:
|
| ---- TEXT REMOVED DUE TO THE SIZE ---
|
| at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)
| at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)
| ... 24 more
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267016#4267016
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4267016
16 years, 5 months
[JBoss Web Services Users] - Basic WebService setup failing (wsconsume 4.2.2 vs 5.1.0 - g
by jpebe001
Hi there @ JBoss web,
Disclaimer: I do not think the following is a bug (because this is pretty basic functionality) but I cannot see what, for the life of us, we are doing wrong or unconventional.
We are using a basic example and we have the following setups
A: JBoss 5.1.0 with CXF WS Stack 3.2.1
B: JBoss 4.2.2 with CXF WS Stack 3.0.2
For both A and B we have the SAME WSDL file (reproduced for completeness hereunder - note that this is automatically generated through the same server class annotation).
| <?xml version="1.0" encoding="UTF-8"?>
| <wsdl:definitions name="testApiService" targetNamespace="http://server.ws.ixaris.com"
| xmlns:ns1="http://schemas.xmlsoap.org/wsdl/soap/http"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| xmlns:tns="http://server.ws.ixaris.com"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| xmlns:xsd="http://www.w3.org/2001/XMLSchema">
| <wsdl:types>
| <xs:schema elementFormDefault="unqualified" targetNamespace="http://server.ws.ixaris.com" version="1.0"
| xmlns:tns="http://server.ws.ixaris.com"
| xmlns:xs="http://www.w3.org/2001/XMLSchema">
| <xs:element name="apiCaller" type="tns:apiCaller"/>
| <xs:element name="apiCallerResponse" type="tns:apiCallerResponse"/>
| <xs:complexType name="apiCaller">
| <xs:sequence>
| <xs:element form="qualified" minOccurs="0" name="arg0" type="tns:testpayment"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="testpayment">
| <xs:sequence>
| <xs:element name="paymentId" type="xs:string"/>
| <xs:element name="userId" type="xs:string"/>
| <xs:element name="amount" type="xs:double"/>
| <xs:element name="currency" type="xs:string"/>
| <xs:element name="date" type="xs:dateTime"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="apiCallerResponse">
| <xs:sequence>
| <xs:element form="qualified" minOccurs="0" name="testApiCallerResult" type="tns:testpaymentconfirmation"/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name="testpaymentconfirmation">
| <xs:sequence>
| <xs:element name="statusCode" type="xs:int"/>
| <xs:element minOccurs="0" name="statusMessage" type="xs:string"/>
| <xs:element minOccurs="0" name="paymentObject" type="tns:testpayment"/>
| </xs:sequence>
| </xs:complexType>
| </xs:schema>
| </wsdl:types>
| <wsdl:message name="apiCaller">
| <wsdl:part element="tns:apiCaller" name="parameters">
| </wsdl:part>
| </wsdl:message>
| <wsdl:message name="apiCallerResponse">
| <wsdl:part element="tns:apiCallerResponse" name="parameters">
| </wsdl:part>
| </wsdl:message>
| <wsdl:portType name="testApiService">
| <wsdl:operation name="apiCaller">
| <wsdl:input message="tns:apiCaller" name="apiCaller">
| </wsdl:input>
| <wsdl:output message="tns:apiCallerResponse" name="apiCallerResponse">
| </wsdl:output>
| </wsdl:operation>
| </wsdl:portType>
| <wsdl:binding name="testApiServiceSoapBinding" type="tns:testApiService">
| <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
| <wsdl:operation name="apiCaller">
| <soap:operation soapAction="" style="document"/>
| <wsdl:input name="apiCaller">
| <soap:body use="literal"/>
| </wsdl:input>
| <wsdl:output name="apiCallerResponse">
| <soap:body use="literal"/>
| </wsdl:output>
| </wsdl:operation>
| </wsdl:binding>
| <wsdl:service name="testApiService">
| <wsdl:port binding="tns:testApiServiceSoapBinding" name="testapiport">
| <soap:address location="http://127.0.0.1:8080/testapiwebservice/testapiservice"/>
| </wsdl:port>
| </wsdl:service>
| </wsdl:definitions>
|
Using the wsconsume tool in the JBoss BIN folder, this WSDL file generates different clients for setups A and B (described above). The main and (possibly only) interesting difference in the service interface is the following:
In A: JBoss 5.1.0 with CXF WS Stack 3.2.1: (class finally generated by Apache CXF 2.2.4)
| @WebResult(name = "testApiCallerResult", targetNamespace = "")
| @.. //other annotations identical!
| public com.ixaris.ws.server.Testpaymentconfirmation apiCaller(
| @WebParam(name = "arg0", targetNamespace = "http://server.ws.ixaris.com")
| com.ixaris.ws.server.Testpayment arg0
| );
|
In B: JBoss 4.2.2 with CXF WS Stack 3.0.2: (class finally generated by JAX-WS RI 2.1.1-b03)
| @WebResult(name = "testApiCallerResult", targetNamespace = "http://server.ws.ixaris.com")
| @.. //other annotations identical!
| public Testpaymentconfirmation apiCaller(
| @WebParam(name = "arg0", targetNamespace = "http://server.ws.ixaris.com")
| Testpayment arg0);
|
As you can see the client generated by the wsconsume tool in setup A does not have a namespace and generates the following exception:
| Exception in thread "main" javax.xml.ws.WebServiceException: class com.ixaris.ws.client.endpoints.ApiCallerResponse do not have a property of the name testApiCallerResult
| at com.sun.xml.internal.ws.client.sei.ResponseBuilder$DocLit.<init>(ResponseBuilder.java:486)
| at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.<init>(SyncMethodHandler.java:171)
| at com.sun.xml.internal.ws.client.sei.SEIStub.<init>(SEIStub.java:67)
| at com.sun.xml.internal.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(WSServiceDelegate.java:544)
| at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:292)
| at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:274)
| at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:267)
| at javax.xml.ws.Service.getPort(Service.java:92)
| at com.ixaris.ws.client.endpoints.TestApiService_Service.getTestapiport(TestApiService_Service.java:62)
| at com.ixaris.ws.client.testapiclient.testApiClientProcess(testapiclient.java:31)
| at com.ixaris.ws.client.testapiclient.main(testapiclient.java:84)
| Caused by: javax.xml.bind.JAXBException: testApiCallerResult is not a valid property on class com.ixaris.ws.client.endpoints.ApiCallerResponse
| at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:910)
| at com.sun.xml.internal.ws.client.sei.ResponseBuilder$DocLit.<init>(ResponseBuilder.java:475)
| ... 10 more
|
Note that if I add this
targetNamespace = "http://server.ws.ixaris.com"
to the Jboss 5.1.0 and CXF 3.2.1 (setup A) WebResult annotation on the interface, everything works fine.
Note: I am running BOTH war files on JBoss 5.1.0 with CXF stack 3.2.1
Any ideas why this is happening ?
Many Thanks
JP
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267001#4267001
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4267001
16 years, 5 months
[jBPM Users] - Re: Can't get pooled task instance list with jbpm & seam - p
by achimh
Ok, I missed the "real answer" for my thread-problem :D
As the annotation do not work the provided seam-objects like pooledTaskInstanceList do not work either. Therefore I had to write a bean that provides this information. It could look like this:
| @Name("taskManager")
| @Stateless
| public class TaskManagerBean implements TaskManagerLocal {
|
| ...
|
| /** Stores the process engine instance. */
| private ProcessEngine processEngine = new Configuration().buildProcessEngine();
|
| /** Stores the user's identity. */
| @In
| private Identity identity;
|
| /** Stores a list of tasks that are assigned to the current user. */
| @DataModel
| private List<Task> assignedTasks;
|
| /** Stores the currently selected assigned Task. */
| @DataModelSelection(value = "assignedTasks")
| private Task assignedTask;
|
| /**
| * Stores a list of tasks that belong the groups the current user is member of and wait for an
| * assignment.
| */
| @DataModel
| private List<Task> groupTasks;
|
| /** Stores the currently selected assigned Task. */
| @DataModelSelection(value = "groupTasks")
| private Task groupTask;
|
| /**
| * Factory method to request the assigned tasks.
| */
| @Factory("assignedTasks")
| public void findAssignedTasks() {
| if (identity.isLoggedIn()) {
| assignedTasks = processEngine.getTaskService().findPersonalTasks(
| identity.getCredentials().getUsername());
| } else {
| assignedTasks = new ArrayList<Task>();
| }
| }
|
| /**
| * Factory method to request the group tasks.
| */
| @Factory("groupTasks")
| public void findGroupTasks() {
| if (identity.isLoggedIn()) {
| groupTasks = processEngine.getTaskService().findGroupTasks(
| identity.getCredentials().getUsername());
| } else {
| groupTasks = new ArrayList<Task>();
| }
| }
|
| public String assignGroupTask() {
| if (identity.isLoggedIn() && groupTask != null) {
| processEngine.getTaskService().assignTask(groupTask.getId(),
| identity.getCredentials().getUsername());
| return TASK_ASSIGNED;
| }
| return null;
| }
| }
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266991#4266991
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266991
16 years, 5 months
[jBPM Users] - Re: Can't get pooled task instance list with jbpm & seam - p
by achimh
Hi,
I just want to give the answer by myself, because I could fix the problem in the meantime and maybe someone is running into the same problems.
The main point for integrating jBPM 4 in Seam (2.2) seems to be that you have to ensure that jBPM 3 is not used in your application. Seam will load its jBPM3 (jbpm-jpdl.jar) component when there is a "<bpm:jbpm>" block in your components.xml - so remove it or at least uncomment it. As in jBPM3 you will have to add the jbpm.jar in your ear-root and register it as java-module in your application.xml like:
| <module>
| <ejb>jboss-seam.jar</ejb>
| </module>
|
| <module>
| <java>jbpm.jar</java>
| </module>
|
Besides these comfiguration issues you cannot use the seam-integrated jbpm-annotations. E.g. to start a process I use this:
| // this won't work: @createProcess(key="MyProcessName")
| public String createMyProcess() {
| ProcessEngine processEngine = new Configuration().buildProcessEngine();
| processEngine.getExecutionService().startProcessInstanceByKey("MyProcessName");
| return "startedMyProcess";
| }
|
Additionally I could not use the Actor class to inject the actor information, although I'm not sure if this might be my fault ;)
Instead I'm using the Seam Identity credentials as actor-id and wrote an own implementation for the IdentitySession interface which handels which groups a user is a member of etc. to determine assignment decisions. To let jBPM4 use this class I had to change my jbpm.cfg.xml to:
| <jbpm-configuration>
| <import resource="jbpm.default.cfg.xml" />
| <import resource="jbpm.tx.hibernate.cfg.xml" />
| <import resource="jbpm.jpdl.cfg.xml" />
| <transaction-context>
| <object class="mypackagename.jbpm.IdentitySessionImpl" />
| </transaction-context>
| <import resource="jbpm.businesscalendar.cfg.xml" />
|
| </jbpm-configuration>
That's my current knowledge about integrating jBPM 4 into Seam. Keep in mind that my application (and the integration) is not finished and there might be more issues to handle. But with these steps I'm able to run at least some simple business processes.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266990#4266990
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266990
16 years, 5 months
[EJB 3.0 Users] - [JBoss 5.1 GA & EJB 3.0] persistence.xml problem : Cannot op
by longbeach
Hi,
Let me first tell you about the content of my EAR archive :
VenteEnLigne.EAR :
| /META-INF
| /META-INF/application.xml
| /META-INF/MANIFEST.MF
| VenteEnLigneClient.jar
| com
| META-INF/persistence.xml
| VenteEnLigneEJB.jar
| com
| META-INF/MANIFEST.MF
| META-INF/orm.xml
| META-INF/persistence.xml
| VenteEnLigneWeb.war
| META-INF/MANIFEST.MF
| WEB-INF/web.xml
|
|
I have developped a servlet in the Web project (VenteEnLigneWeb). It calls a stateless session bean (StockTimerService.java) that tries to execute a JPQ query with an entity bean
developped in the EJB project.
Part of the code of StockTimerService.java is :
| ...
| @PersistenceContext(unitName="VenteEnLigneModuleEJB")
| private EntityManager em;
| ...
| List stocks = em.createQuery("from Stock").getResultList();
|
The persistent unit VenteEnLigneModuleEJB is a persistent unit that is defined inside VenteEnLigneEJB.jar/META-INF/persistence.xml.
Its transaction type is JTA.
I get the following errors :
|
| 0:37:22,853 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: null
| 10:37:22,853 ERROR [JDBCExceptionReporter] Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -3f57c7ff:cec5:4b0a5793:64 status: ActionStatus.ABORT_ONLY >); - nested throwable: (org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -3f57c7ff:cec5:4b0a5793:64 status: ActionStatus.ABORT_ONLY >))
| 10:37:22,926 ERROR [[TestTimer]] "Servlet.service()" pour la servlet TestTimer a gïÿýnïÿýrïÿý une exception
| javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection
| at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:77)
| at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
| at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:421)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:85)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
| at $Proxy368.invoke(Unknown Source)
| at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
| at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
| at $Proxy367.verifierStocks(Unknown Source)
| at com.eni.dvtejb.web.TestTimer.doGet(TestTimer.java:40)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
| 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(Unknown Source)
| Caused by: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection
| at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614)
| at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:76)
| at com.eni.dvtejb.metier.sessions.StockTimerService.verifierStocks(StockTimerService.java:64)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
| at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
| at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
| at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
| at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_6740524.invoke(InvocationContextInterceptor_z_fillMethod_6740524.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
| at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_6740524.invoke(InvocationContextInterceptor_z_setup_6740524.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
| ... 46 more
| Caused by: org.hibernate.exception.GenericJDBCException: Cannot open connection
| at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126)
| at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114)
| at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
| at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52)
| at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:449)
| at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167)
| at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161)
| at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1573)
| at org.hibernate.loader.Loader.doQuery(Loader.java:696)
| at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
| at org.hibernate.loader.Loader.doList(Loader.java:2228)
| at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125)
| at org.hibernate.loader.Loader.list(Loader.java:2120)
| at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401)
| at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:361)
| at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196)
| at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1148)
| at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
| at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:67)
| ... 79 more
| Caused by: org.jboss.util.NestedSQLException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -3f57c7ff:cec5:4b0a5793:64 status: ActionStatus.ABORT_ONLY >); - nested throwable: (org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -3f57c7ff:cec5:4b0a5793:64 status: ActionStatus.ABORT_ONLY >))
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)
| at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:46)
| at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
| ... 93 more
| Caused by: org.jboss.resource.JBossResourceException: Could not enlist in transaction on entering meta-aware object!; - nested throwable: (javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -3f57c7ff:cec5:4b0a5793:64 status: ActionStatus.ABORT_ONLY >)
| at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:409)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnectManagedConnection(BaseConnectionManager2.java:625)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:499)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
| ... 95 more
| Caused by: javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: -3f57c7ff:cec5:4b0a5793:64 status: ActionStatus.ABORT_ONLY >
| at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener$TransactionSynchronization.checkEnlisted(TxConnectionManager.java:879)
| at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.enlist(TxConnectionManager.java:675)
| at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:403)
| ... 99 more
|
What is wrong ?
How does JBoss call the various persistence.xml files it encounters in an archive with several projects ?
Is it something with the transaction type : JTA / RESOURCE_LOCAL ?
Thanks in advance for helping.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266989#4266989
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266989
16 years, 5 months