You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by an...@bt.com on 2005/10/28 17:30:57 UTC
axis1.2.1 - errors running interop example
Hi
I want to run kandula under axis1.2.1. I was able to build the
distribution using axis1.2.1 (replacing appropriate entries in
project.xml). When I run the interop example I get the following error
[junit] Running InteropPortTypeRPCServiceTestCase
[junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 1.891
sec
[junit] Output:
[junit] - Exception:
[junit] java.io.IOException: Non nillable element
'participantProtocolService' is null.
[junit] at
org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.jav
a:215)
<longer stacktrace to follow>
Its basically the same error as described at
http://www.mail-archive.com/kandula-dev@ws.apache.org/msg00032.html
I suppose this is due to axis1.2 Serializer not accepting null objects.
I added some debug statements to the kandula code. From that I can tell
that the error is triggered by TransactionManager.begin () which at some
stage calls CoordinationContext.register () with a null
endpointreference.
To be honest I am not very familiar with kandula but I tried to work
around by passing an initialized EPR (with some address) to the method
call and I got rid of the exception that way, but now on the server side
in InteropServiceSoapBindingImpl.commit () the state of the transaction
received from the TransactionManager is STATUS_NO_TRANSACTION
I don't know how to proceed from here. We would like to use kandula with
the forthcoming versions of the axis1 branch as some other projects we
required have no intention to switch on the axis2 branch so far. Any
help would be much appreciated
Regards,
Andreas Maierhofer
Re: axis1.2.1 - errors running interop example
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Thilina Gunarathne <cs...@gmail.com>:
> >
> > [junit] java.io.IOException: Non nillable element
> > 'participantProtocolService' is null.
> >
> > [junit] at org.apache.axis.encoding.ser.BeanSerializer.serialize(
> > BeanSerializer.java:215)
> >
I made a quick(&dirty) fix. Please do an SVN-update. Also make sure that you
use Axis 1.3 (I will update the user guide shortly.)
> > I suppose this is due to axis1.2 Serializer not accepting null objects. I
> > added some debug statements to the kandula code. From that I can tell that
> > the error is triggered by TransactionManager.begin () which at some stage
> > calls CoordinationContext.register () with a null endpointreference.
This seems to be the case.
> >
> > To be honest I am not very familiar with kandula but I tried to work
> > around by passing an initialized EPR (with some address) to the method
> call
> > and I got rid of the exception that way, but now on the server side in
> > InteropServiceSoapBindingImpl.commit () the state of the transaction
> > received from the TransactionManager is STATUS_NO_TRANSACTION
When I tried interop test I did not get this problem.
It could be that your server side handlers are not
deployed properly. Could you please compare the output
you get from Tomcat with what I have attached below and let me know
where things differ.
Thanks
--dasarath
------------------------------------------------
[InteropServiceSoapBindingImpl] commit() STATUS_ACTIVE
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b088c8
10-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] xid://?formatId=258,globalTransactionId=uuid:b08
8c810-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0 tx.hashCode= -141997895
0
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b088c810
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] isSameRM= true
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b088c8
10-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] rollback() STATUS_ACTIVE
[DummyXAResource] isSameRM= false
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b088c8
10-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] xid://?formatId=258,globalTransactionId=uuid:b08
8c810-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0 tx.hashCode= -141997895
0
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b088c810
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b088c810
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] prepare return XAResource.XA_OK
[DummyXAResource] prepare throw new XAException(XAException.XAER_RMERR)
- Got XAException from resource.prepare: Cannot send res.prepare:javax.transacti
on.xa.XAException (error code = -3) --null
- Resource replied rollback to prepare
[DummyXAResource] rollback xid= xid://?formatId=258,globalTransactionId=uuid:b08
8c810-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] rollback xid= xid://?formatId=258,globalTransactionId=uuid:b08
8c810-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] commit() STATUS_ACTIVE
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b10264
e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] xid://?formatId=258,globalTransactionId=uuid:b10
264e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0 tx.hashCode= 354258706
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b10264e0
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] isSameRM= true
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b10264
e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] commit() STATUS_ACTIVE
[DummyXAResource] isSameRM= false
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b10264
e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] xid://?formatId=258,globalTransactionId=uuid:b10
264e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0 tx.hashCode= 354258706
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b10264e0
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b10264e0
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] rollback xid= xid://?formatId=258,globalTransactionId=uuid:b10
264e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] rollback xid= xid://?formatId=258,globalTransactionId=uuid:b10
264e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
------------------------------------------------
> >
> > I don't know how to proceed from here. We would like to use kandula with
> > the forthcoming versions of the axis1 branch as some other projects we
> > required have no intention to switch on the axis2 branch so far. Any help
> > would be much appreciated
> >
> > Regards,
> >
> > Andreas Maierhofer
> >
> >
>
>
> --
> "May the SourcE be with u"
> http://webservices.apache.org/~thilina/
> http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: axis1.2.1 - errors running interop example
Posted by Dasarath Weeratunge <dw...@purdue.edu>.
Quoting Thilina Gunarathne <cs...@gmail.com>:
> >
> > [junit] java.io.IOException: Non nillable element
> > 'participantProtocolService' is null.
> >
> > [junit] at org.apache.axis.encoding.ser.BeanSerializer.serialize(
> > BeanSerializer.java:215)
> >
I made a quick(&dirty) fix. Please do an SVN-update. Also make sure that you
use Axis 1.3 (I will update the user guide shortly.)
> > I suppose this is due to axis1.2 Serializer not accepting null objects. I
> > added some debug statements to the kandula code. From that I can tell that
> > the error is triggered by TransactionManager.begin () which at some stage
> > calls CoordinationContext.register () with a null endpointreference.
This seems to be the case.
> >
> > To be honest I am not very familiar with kandula but I tried to work
> > around by passing an initialized EPR (with some address) to the method
> call
> > and I got rid of the exception that way, but now on the server side in
> > InteropServiceSoapBindingImpl.commit () the state of the transaction
> > received from the TransactionManager is STATUS_NO_TRANSACTION
When I tried interop test I did not get this problem.
It could be that your server side handlers are not
deployed properly. Could you please compare the output
you get from Tomcat with what I have attached below and let me know
where things differ.
Thanks
--dasarath
------------------------------------------------
[InteropServiceSoapBindingImpl] commit() STATUS_ACTIVE
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b088c8
10-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] xid://?formatId=258,globalTransactionId=uuid:b08
8c810-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0 tx.hashCode= -141997895
0
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b088c810
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] isSameRM= true
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b088c8
10-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] rollback() STATUS_ACTIVE
[DummyXAResource] isSameRM= false
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b088c8
10-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] xid://?formatId=258,globalTransactionId=uuid:b08
8c810-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0 tx.hashCode= -141997895
0
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b088c810
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b088c810
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] prepare return XAResource.XA_OK
[DummyXAResource] prepare throw new XAException(XAException.XAER_RMERR)
- Got XAException from resource.prepare: Cannot send res.prepare:javax.transacti
on.xa.XAException (error code = -3) --null
- Resource replied rollback to prepare
[DummyXAResource] rollback xid= xid://?formatId=258,globalTransactionId=uuid:b08
8c810-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] rollback xid= xid://?formatId=258,globalTransactionId=uuid:b08
8c810-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] commit() STATUS_ACTIVE
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b10264
e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] xid://?formatId=258,globalTransactionId=uuid:b10
264e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0 tx.hashCode= 354258706
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b10264e0
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] isSameRM= true
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b10264
e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] commit() STATUS_ACTIVE
[DummyXAResource] isSameRM= false
[DummyXAResource] start xid= xid://?formatId=258,globalTransactionId=uuid:b10264
e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[InteropServiceSoapBindingImpl] xid://?formatId=258,globalTransactionId=uuid:b10
264e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0 tx.hashCode= 354258706
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b10264e0
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] end xid= xid://?formatId=258,globalTransactionId=uuid:b10264e0
-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] rollback xid= xid://?formatId=258,globalTransactionId=uuid:b10
264e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
[DummyXAResource] rollback xid= xid://?formatId=258,globalTransactionId=uuid:b10
264e0-483d-11da-8540-9364396d1cfa,branchQualifier=uuid:0
------------------------------------------------
> >
> > I don't know how to proceed from here. We would like to use kandula with
> > the forthcoming versions of the axis1 branch as some other projects we
> > required have no intention to switch on the axis2 branch so far. Any help
> > would be much appreciated
> >
> > Regards,
> >
> > Andreas Maierhofer
> >
> >
>
>
> --
> "May the SourcE be with u"
> http://webservices.apache.org/~thilina/
> http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
>
---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org
Re: axis1.2.1 - errors running interop example
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
Please check whether you have all the handlers (Addressing and Transaction)
deployed....
You can have a look at the Tcp monitor output to determine whether the
handlers are engaged.
Pls try to post the TCPmon message traces, which will help a lot in
identifying the problem.
Thanks,
~Thilina
On 10/28/05, andreas.maierhofer@bt.com <an...@bt.com> wrote:
>
> Hi
>
> I want to run kandula under axis1.2.1. I was able to build the
> distribution using axis1.2.1 (replacing appropriate entries in project.xml).
> When I run the interop example I get the following error
>
> [junit] Running InteropPortTypeRPCServiceTestCase
>
> [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 1.891 sec
>
> [junit] Output:
>
> [junit] - Exception:
>
> [junit] java.io.IOException: Non nillable element
> 'participantProtocolService' is null.
>
> [junit] at org.apache.axis.encoding.ser.BeanSerializer.serialize(
> BeanSerializer.java:215)
>
> <longer stacktrace to follow>
>
> Its basically the same error as described at
> http://www.mail-archive.com/kandula-dev@ws.apache.org/msg00032.html
>
> I suppose this is due to axis1.2 Serializer not accepting null objects. I
> added some debug statements to the kandula code. From that I can tell that
> the error is triggered by TransactionManager.begin () which at some stage
> calls CoordinationContext.register () with a null endpointreference.
>
> To be honest I am not very familiar with kandula but I tried to work
> around by passing an initialized EPR (with some address) to the method call
> and I got rid of the exception that way, but now on the server side in
> InteropServiceSoapBindingImpl.commit () the state of the transaction
> received from the TransactionManager is STATUS_NO_TRANSACTION
>
> I don't know how to proceed from here. We would like to use kandula with
> the forthcoming versions of the axis1 branch as some other projects we
> required have no intention to switch on the axis2 branch so far. Any help
> would be much appreciated
>
> Regards,
>
> Andreas Maierhofer
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
Re: axis1.2.1 - errors running interop example
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi,
Please check whether you have all the handlers (Addressing and Transaction)
deployed....
You can have a look at the Tcp monitor output to determine whether the
handlers are engaged.
Pls try to post the TCPmon message traces, which will help a lot in
identifying the problem.
Thanks,
~Thilina
On 10/28/05, andreas.maierhofer@bt.com <an...@bt.com> wrote:
>
> Hi
>
> I want to run kandula under axis1.2.1. I was able to build the
> distribution using axis1.2.1 (replacing appropriate entries in project.xml).
> When I run the interop example I get the following error
>
> [junit] Running InteropPortTypeRPCServiceTestCase
>
> [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 1.891 sec
>
> [junit] Output:
>
> [junit] - Exception:
>
> [junit] java.io.IOException: Non nillable element
> 'participantProtocolService' is null.
>
> [junit] at org.apache.axis.encoding.ser.BeanSerializer.serialize(
> BeanSerializer.java:215)
>
> <longer stacktrace to follow>
>
> Its basically the same error as described at
> http://www.mail-archive.com/kandula-dev@ws.apache.org/msg00032.html
>
> I suppose this is due to axis1.2 Serializer not accepting null objects. I
> added some debug statements to the kandula code. From that I can tell that
> the error is triggered by TransactionManager.begin () which at some stage
> calls CoordinationContext.register () with a null endpointreference.
>
> To be honest I am not very familiar with kandula but I tried to work
> around by passing an initialized EPR (with some address) to the method call
> and I got rid of the exception that way, but now on the server side in
> InteropServiceSoapBindingImpl.commit () the state of the transaction
> received from the TransactionManager is STATUS_NO_TRANSACTION
>
> I don't know how to proceed from here. We would like to use kandula with
> the forthcoming versions of the axis1 branch as some other projects we
> required have no intention to switch on the axis2 branch so far. Any help
> would be much appreciated
>
> Regards,
>
> Andreas Maierhofer
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina