Re: [jboss-user] [JCA] - XA Recovery
by Ben Ritchie
Ben Ritchie [http://community.jboss.org/people/BenR] replied to the discussion
"XA Recovery"
To view the discussion, visit: http://community.jboss.org/message/551041#551041
--------------------------------------------------------------
> Jonathan Halliday wrote:
>
>
> Application writer? Last I heard you were an MQ dev at IBM, not an end user.
It's not mutually exclusive. If people are using this in production unaware that they can't do transaction recovery then i'm quite keen to know about it and (if necessary) point them at the relevant config.
> Jonathan Halliday wrote:
>
> - you're basically referring to JCA 1.5 section 12.5.2 I think.
>
>
> ResourceAdapter.getXAResources(javax.resource.spi.ActivationSpec[] activationSpecs) I'm guessing that's an implementation decision based on the assumption that a call to ManagedConnection.getXAResource().recover() will return equivalent information instead.
I don't think it's a safe assumption though - you can define an activationSpec without a corresponding MCF, so there's no guarantee you can get the necessary information to drive recovery
12.5.2 reads to me as if the server must call ResourceAdapter.getXAResources(...) to do recovery, although there may be something elsewhere that overrides that section - it's been a while since I read the spec in detail.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551041#551041]
Start a new discussion in JCA at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
Re: [jboss-user] [JBoss Web Services CXF] - Continuing problem with XTS WS-T tests in AS trunk/CXF 2.2.9
by Andrew Dinn
Andrew Dinn [http://community.jboss.org/people/adinn] replied to the discussion
"Continuing problem with XTS WS-T tests in AS trunk/CXF 2.2.9"
To view the discussion, visit: http://community.jboss.org/message/551040#551040
--------------------------------------------------------------
Hi Jim,
Apologies for the delay in getting bak. It's been a long haul working through the rets of the changes needed after you fixed the soap fault delivery problem.
> Jim Ma wrote:
>
> I attched the pached jars and source files to https://jira.jboss.org/browse/JBWS-3069 https://jira.jboss.org/browse/JBWS-3069. Please let me know if you have furthur CXF issues. Thanks.
The patches work fine and soap fault delivery is happening as expected.
Unfortunately, I then ran into a further problem which meant that I was not able to employ a separate SOAP service to dispatch/catch the faults. CXF includes metadata in its W3C endpoints so I can no longer take an endpoint derived from one of the WS-T services and pass it to the getPort method of my SoapFaultService. This means that I have had no choice but to explicitly include the soap fault delivery method in my WS-T service WSDL and generate corresponding methods on the SEI interfaces and implementation beans.
So, I am now having to use a non-standard WSDL and non-standard endpoint for these services. We can live with this because the service is a conservative extension of the expected implementation (i.e. it does everything expected and then some).
So, it looks as if you can close JBWS-3069.
I ran into one other problem which does not break anything immediately but will be an issue for interoperability, specifically with Microsoft. When my services get an incoming request they normally need to hand back an endpoint for a continuation message. If the incoming request arrives via an https scheme URL then the endpoint for the the continuation should be created using an https scheme. So, in the WebMethod implementation I use code as follows to identify the request scheme
> @WebMethod(...)
> public void foo()
> {
>
> MessageContext ctx = webServiceCtx.getMessageContext();
> HttpServletRequest request = (HttpServletRequest)ctx.get(MessageContext.SERVLET_REQUEST);
> boolean isSecure = "https".equals(request.getScheme());
> . . .
The problem is that when foo is a OneWay method request.getScheme always returns null. Now this does not break anything (it did when I did the equals test the other way round which is why I spotted it :-) but it does mean that I always think the client is contacting the services via a non-secure URL. Now, Microsoft's WSTX always uses https and it will throw up if handed an http endpont for the continuation message. So, I need a reliable way to obtain the request scheme when the message is OneWay. Any ideas? Or do I have to raise a JIRA feature request for this?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551040#551040]
Start a new discussion in JBoss Web Services CXF at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
[JBoss Web Services Metro] - Jboss 4.2.3 IllegalArgumentException for Invoking webservice in JDK1.6
by Rizwan P
Rizwan P [http://community.jboss.org/people/RizwanP] created the discussion
"Jboss 4.2.3 IllegalArgumentException for Invoking webservice in JDK1.6"
To view the discussion, visit: http://community.jboss.org/message/551031#551031
--------------------------------------------------------------
Hi,
I am getting strange error on different jboss instances while invoking the webservice.
The configuration for both the server instance is same no change just a duplicate copy of other.
Below is the error I am receiving while invoking the webservice call at first time, and after that the working of client is halt.
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImple.newInstance0(Native Method)
....
at javax.xml.soap.FactoryFinder.newInstance(FactoryFinder.java:55)
....
at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:144)
at com.sun.xml.ws.api.SOAPVersion.<init>(SOAPVersion.java:178)
....
Caused by: java.lang.IllegalArgumentException: com.sun.xml.internal.messaging.saaj.soap.LocalStrings != com.sun.xml.messaging.saaj.soap.LocalStrings
at java.util.logging.Logger.getLogger(Logger.java:314)
at com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImple.<init>(SAAJMetaFactoryImpl.java:52)
Please provide suggestion how to resolve this problem.
saaj-impl.jar version : 1.3 (Present at the server's jbossws.sar directory and nowhere on the instance)
JDK : 1.6.013
Jboss : 4.2.3
Jboss Metro : 3.1.1.GA
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551031#551031]
Start a new discussion in JBoss Web Services Metro at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
Re: [jboss-user] [JCA] - XA Recovery
by Jonathan Halliday
Jonathan Halliday [http://community.jboss.org/people/jhalliday] replied to the discussion
"XA Recovery"
To view the discussion, visit: http://community.jboss.org/message/551026#551026
--------------------------------------------------------------
> i'm looking at inbound recovery (via the ResourceAdapter.getXAResouces(...) call) and from the perspective of an application writer
Application writer? Last I heard you were an MQ dev at IBM, not an end user. The first part of that sentence does make sense though - you're basically referring to JCA 1.5 section 12.5.2 I think.
> and it came as something of a surprise that this might not work 'out of the box'.
If you can say that with a straight face you've not been watching enough youtube :-)
As far an I can tell from a quick poke though the JCA code, it does not call ResourceAdapter.getXAResources(javax.resource.spi.ActivationSpec[] activationSpecs) I'm guessing that's an implementation decision based on the assumption that a call to ManagedConnection.getXAResource().recover() will return equivalent information instead.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551026#551026]
Start a new discussion in JCA at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
Re: [jboss-user] [jBPM] - JBPM Exception when running workflow
by Stephen Sitton
Stephen Sitton [http://community.jboss.org/people/stevesitton] replied to the discussion
"JBPM Exception when running workflow"
To view the discussion, visit: http://community.jboss.org/message/551011#551011
--------------------------------------------------------------
Hi Maciej,
Thanks for the response. Attached is the test (+additional files) which displays the error (org.jbpm.test.CustomTest). The process definition (process.jpdl.xml) is also in the zip. This is using jBPM 4.0.
The output from the test is:
Processing 2 files in directory "testfiles"
Processing file "file2.zip"
Extracting the file :file2.xml
Extracted the file :file2.xml
Data Convert message - 384
Data Convert message - 385
Data Convert message - 386
Data Convert message - 387
Data Convert message - 388
Data Convert message - 389
Data Convert message - 381
Data Convert message - 382
Extracting the file :file1.xml
Extracted the file :file1.xml
Data Convert message - 112
Data Convert message - 113
Data Convert message - 114
Data Convert message - 111
Data Convert message - 115
Data Convert message - 116
Data Convert message - 117
Data Convert message - 118
Data Convert message - 119
The exception I get is...
java.lang.NullPointerException
at org.jbpm.pvm.internal.model.op.ExecuteEventListener.perform(ExecuteEventListener.java:68)
at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:637)
at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperation(ExecutionImpl.java:597)
at org.jbpm.pvm.internal.model.ExecutionImpl.start(ExecutionImpl.java:201)
at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:64)
at org.jbpm.pvm.internal.cmd.StartProcessInstanceInLatestCmd.execute(StartProcessInstanceInLatestCmd.java:37)
at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.startProcessInstanceByKey(ExecutionServiceImpl.java:66)
at org.jbpm.test.CustomTest.testProcess(CustomTest.java:24)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:154)
at org.jbpm.test.BaseJbpmTestCase.runTest(BaseJbpmTestCase.java:80)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Please let me know if there I something I'm doing wrong or if there is a problem in jbpm.
thanks
Steve
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551011#551011]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months