[JBossWS] - Transaction Not Allowed
by subramaniam.venkat
Hello All,
I have exposed an SLSB as an web-service.
There is no transaction on this SLSB which i have implemented.
But this SLSB makes calls to Springs Beans on which transaction has been implemented.
I am getting the below error and i am not able to find a reason for this.
I am using Jboss-4.0.3-SP1 and JDK142.
Can someone give me some pointer.
Thanks in advance,
Subramaniam V
| java.rmi.ServerException: EJBException:; nested exception is:
| javax.ejb.EJBException: Transaction not allowed
| at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:352)
| at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:125)
| at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)
| at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:613)
| at org.jboss.ejb.Container.invoke(Container.java:894)
| at sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
| at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:155)
| at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:104)
| at org.jboss.invocation.InvokerInterceptor.invokeLocal(InvokerInterceptor.java:179)
| at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:165)
| at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
| at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
| at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:169)
| at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
| at $Proxy98.create(Unknown Source)
| at sun.reflect.GeneratedMethodAccessor322.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.net.axis.server.EJBProvider.makeNewServiceObject(EJBProvider.java:140)
| at org.jboss.axis.providers.java.JavaProvider.getNewServiceObject(JavaProvider.java:280)
| at org.jboss.axis.providers.java.JavaProvider.getServiceObject(JavaProvider.java:131)
| at org.jboss.axis.providers.java.JavaProvider.invoke(JavaProvider.java:335)
| at org.jboss.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:73)
| at org.jboss.axis.SimpleChain.doVisiting(SimpleChain.java:160)
| at org.jboss.axis.SimpleChain.invoke(SimpleChain.java:123)
| at org.jboss.axis.handlers.soap.SOAPService.invoke(SOAPService.java:560)
| at org.jboss.axis.server.AxisServer.invoke(AxisServer.java:355)
| at org.jboss.axis.transport.http.AxisServlet.doPost(AxisServlet.java:911)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.jboss.axis.transport.http.AxisServletBase.service(AxisServletBase.java:370)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
| at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
| at java.lang.Thread.run(Thread.java:534)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069148#4069148
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069148
18Â years, 8Â months
[JBoss Seam] - Re: Is there a JBossWS client example for invoking a Seam ws
by lowecg2004
Shane,
Thanks for your reply, I'll give the new build a go.
As for the session ID, I've been trying to add a cookie to a client generated by the JBossWS 2.0.0.GA wsconsume tool without any luck. As far as I understand session support in the client, it looks like you can instruct the client to participate in a session which it creates and manages itself. I was able to do this and get the resulting JSESSIONID cookie from the WS call. However I've not yet found a way to make a WS participate in an existing session (i.e. set my own JSESSIONID Cookie header).
I believe there are some issues with session management in the 2.0.0 release. In particular, a session may be created but appears to get lost during subsequent requests. My prefered approach would have been to add the JSESSIONID myself rather than letting the client handle it, that way I can have servlets/web services/you name it all part of the same session. I'd also posted on the JBossWS regarding session management however I've yet to receive a reply:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112660
I've had an equally tough time adding a SOAP header from a JAX-WS 2.0 client runtime (JDK 6) in order to specify the conversation ID. Under JAX-WS 2.1 it looks very straight forward, but I've not found a portable solution for JAX-WS 2.0. I'm probably missing something obvious, but variations in standards and versions and even behaviour between vendors has just left me completely confused and bewildered.
What clients have you guys been using for your testing?
Cheers,
Chris.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069143#4069143
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069143
18Â years, 8Â months
[JBoss jBPM] - Help to design a process + API call : Dynamic Task
by JeanGuyer
Hi,
I have a process to design , it's an approval process :
A person ask to close/delete a business entity in the database. Depend on the nature of the entity , we extract N person (it can be 1 2 3 4 , etc).
Each person will receive a Task Assignment at the same time (like a fork) : they must approve or reject.
If one of them , reject , the others assignment will be deleted , and a message will be sent to the initial asker. If everyone approve , the entity is deleted and a message is sent to all of them (asker and approvers)
Each process instance must have the same process definition (for stats purpose).
I have look a little and i have found getTaskMgmtInstance().addTaskInstance
getTaskMgmtDefinition().addTask
Obviously a dynamic Task must be linked to a Tasknode for later more complex process.
Sorry for the bad english.
Hope to have a answer soon :)
Best Regards,
Jean Guyer
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069141#4069141
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069141
18Â years, 8Â months