ALE SE - where did it go?

5 messages Options
Embed this post
Permalink
Michael.Czapski

ALE SE - where did it go?

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)
Hello.

I tried to find the ALE SE (Auditing, Logging and Exception Handling SE) in the component list but it is not there either as a released, beta or incubator component, yet, there are wiki pages and reference to it all over the place. What happened to it? Is it going to happen? What options are there for ALE for OpenESB / GlassFish ESB?

Thanks in advance

Michael
--

--

Podcast 1   Podcast 2

 

Michael Czapski, BSc Computing, MSc eBus.Tech.
Principal Field Technologist, Software
SOA/BI/Java CAPS

Sun Microsystems
33 Berry Street, North Sydney
NSW 2060 Australia
Phone +61 2 9466 9427
Email [hidden email]

Blog: http://blogs.sun.com/javacapsfieldtech/

LinkedIn: MichaelCzapski

Skype: michaelczapski

Screencasts and Document Archives: http://mediacast.sun.com/users/Michael.Czapski-Sun

JavaOne 2008 SYS-CON.TV Interview with Michael Czapski and Brendan Marry: http://tv.sys-con.com/node/674561

 


Gabe-2

Re: ALE SE - where did it go?

Reply Threaded More More options
Print post
Permalink
Hello Michael - we put ALE on hold for now - the idea is that Fuji v3
interceptors and other mechanisms in v3 will provide the equivalent
functionality.
Thanks
Gabe

Michael Czapski, Principal Field Technologist, ANZ APS, SOA/BI/Java CAPS
wrote:

> Hello.
>
> I tried to find the ALE SE (Auditing, Logging and Exception Handling
> SE) in the component list but it is not there either as a released,
> beta or incubator component, yet, there are wiki pages and reference
> to it all over the place. What happened to it? Is it going to happen?
> What options are there for ALE for OpenESB / GlassFish ESB?
>
> Thanks in advance
>
> Michael
> --
>
> --
>
> <http://www.sun.com/books/catalog/java_caps.xml>
>
> Podcast 1
> <http://mediacast.sun.com/users/Michael.Czapski-Sun/media/JavaCAPS_Czapski_Marry_P1of2Java/details>  
> Podcast 2
> <http://mediacast.sun.com/users/Michael.Czapski-Sun/media/JavaCAPS_Czapski_Marry_P2of2Java/details>
>
>
>
>
>  
>
>
>
> *Michael Czapski, BSc Computing, MSc eBus.Tech.*
> Principal Field Technologist, Software
> SOA/BI/Java CAPS
>
> *Sun Microsystems*
> 33 Berry Street, North Sydney
> NSW 2060 Australia
> Phone +61 2 9466 9427
> Email [hidden email] <mailto:[hidden email]>
>
> Blog: http://blogs.sun.com/javacapsfieldtech/
>
> LinkedIn: MichaelCzapski <http://www.linkedin.com/in/michaelczapski>
>
> Skype: michaelczapski <skype:michaelczapski>
>
> Screencasts and Document Archives:
> http://mediacast.sun.com/users/Michael.Czapski-Sun
>
> JavaOne 2008 SYS-CON.TV Interview with Michael Czapski and Brendan
> Marry: http://tv.sys-con.com/node/674561
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Saurabh K Saxena

Unable to load jar to netbean 6.1 - pojo program

Reply Threaded More More options
Print post
Permalink

I uploaded jar file in libraries and at run time it is unable to find this jar file and throwing this error. I am using JCAPS 6U1(Open ESB, JBI), POJO, BPEL and Composite Application. Kindly advice.

[#|2009-10-26T16:07:25.590-0700|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=51;_ThreadName=pojo-se-1;POJO Provider Class=class org.glassfish.openesb.InformaticaPOJOProvider;ServiceUnit=CaInformatica-jseInformaticaInterface;_RequestID=30e8bd9e-d10e-42b7-9b2e-ad9708cae387;|
<status><severity>4</severity><description>!The shared object / DLL CM_JavaAPI could not be loaded. This could be the result of a problematic installation, a wrong library search path, or an attempt to load a 32/64-bit library from a 64/32-bit process. Operating System error message: no CM_JavaAPI in java.library.path!</description></status>|#]

[#|2009-10-26T16:07:25.606-0700|SEVERE|sun-appserver9.1|org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor|_ThreadID=51;_ThreadName=pojo-se-1;POJO Provider Class=class org.glassfish.openesb.InformaticaPOJOProvider;ServiceUnit=CaInformatica-jseInformaticaInterface;_RequestID=30e8bd9e-d10e-42b7-9b2e-ad9708cae387;|The log message is null.
java.lang.NullPointerException
        at org.glassfish.openesb.InformaticaPOJOProvider.receive(InformaticaPOJOProvider.java:99)
        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 org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor.executePojoOperation(InOutExecutor.java:76)
        at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.executePojoOperation(InMsgTask.java:231)
        at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.run(InMsgTask.java:116)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
|#]

[#|2009-10-26T16:07:25.621-0700|WARNING|sun-appserver9.1|com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl|_ThreadID=52;_ThreadName=BPELSEInOutThread9;Process Instance Id=10.24.10.42:49253bbf:1249317c5fe:-7fe7;Service Assembly Name=CaInformatica;BPEL Process Name=BpelInformaticaInterface;_RequestID=5f82058c-5091-45c0-a9aa-627e845c9cf9;|BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>null</jbi:part></jbi:message>
com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=PojoLinkInformatica, portType={http://openesb.glassfish.org/InformaticaPOJOProvider/}InformaticaPOJOProviderInterface, operation=InformaticaPOJOProviderOperation)
BPCOR-6129:Line Number is 34
BPCOR-6130:Activity Name is Invoke1
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:974)
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:547)
        at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:182)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:147)
        at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1046)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:278)
        at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1293)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:402)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)
        at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)
Caused by: java.lang.NullPointerException
        at org.glassfish.openesb.InformaticaPOJOProvider.receive(InformaticaPOJOProvider.java:99)
        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 org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor.executePojoOperation(InOutExecutor.java:76)
        at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.executePojoOperation(InMsgTask.java:231)
        at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.run(InMsgTask.java:116)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
|#]

[#|2009-10-26T16:09:43.060-0700|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=53;_ThreadName=httpWorkerThread-4848-3;|Stopping service assembly CaInformatica on target server.|#]


Regards,
Saurabh Saxena

*IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. *

Saurabh K Saxena

Re: Unable to load jar to netbean 6.1 - pojo program

Reply Threaded More More options
Print post
Permalink

I put this jar file in all possible lib directories for java1.6, glassfish app server.

Here is our java.library.path from my windows xp desktop -
C:\Program Files\Informatica\DataTransformation\api\lib;C:\Program Files\Informatica\DataTransformation\bin;C:\JavaCAPS6\appserver\lib;C:\JavaCAPS6\appserver\bin|#]


Still getting that exception -
The shared object / DLL CM_JavaAPI could not be loaded. This could be the result of a problematic installation, a wrong library search path, or an attempt to load a 32/64-bit library from a 64/32-bit process. Operating System error message: no CM_JavaAPI in java.library.path!|#]




Regards,
Saurabh S,   RITS CDX /EDI /TM,   desk:  (206) 332-5957


From: "Saurabh K Saxena" <[hidden email]>
To: [hidden email]
Date: 10/26/2009 11:32 PM
Subject: Unable to load jar to netbean 6.1 - pojo program






I uploaded jar file in libraries and at run time it is unable to find this jar file and throwing this error. I am using JCAPS 6U1(Open ESB, JBI), POJO, BPEL and Composite Application. Kindly advice.


[#|2009-10-26T16:07:25.590-0700|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=51;_ThreadName=pojo-se-1;POJO Provider Class=class org.glassfish.openesb.InformaticaPOJOProvider;ServiceUnit=CaInformatica-jseInformaticaInterface;_RequestID=30e8bd9e-d10e-42b7-9b2e-ad9708cae387;|

<status><severity>4</severity><description>!The shared object / DLL CM_JavaAPI could not be loaded. This could be the result of a problematic installation, a wrong library search path, or an attempt to load a 32/64-bit library from a 64/32-bit process. Operating System error message: no CM_JavaAPI in java.library.path!</description></status>|#]


[#|2009-10-26T16:07:25.606-0700|SEVERE|sun-appserver9.1|org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor|_ThreadID=51;_ThreadName=pojo-se-1;POJO Provider Class=class org.glassfish.openesb.InformaticaPOJOProvider;ServiceUnit=CaInformatica-jseInformaticaInterface;_RequestID=30e8bd9e-d10e-42b7-9b2e-ad9708cae387;|The log message is null.

java.lang.NullPointerException

       at org.glassfish.openesb.InformaticaPOJOProvider.receive(InformaticaPOJOProvider.java:99)

       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 org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor.executePojoOperation(InOutExecutor.java:76)

       at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.executePojoOperation(InMsgTask.java:231)

       at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.run(InMsgTask.java:116)

       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)

       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)

       at java.lang.Thread.run(Thread.java:619)

|#]


[#|2009-10-26T16:07:25.621-0700|WARNING|sun-appserver9.1|com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl|_ThreadID=52;_ThreadName=BPELSEInOutThread9;Process Instance Id=10.24.10.42:49253bbf:1249317c5fe:-7fe7;Service Assembly Name=CaInformatica;BPEL Process Name=BpelInformaticaInterface;_RequestID=5f82058c-5091-45c0-a9aa-627e845c9cf9;|BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {
http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>null</jbi:part></jbi:message>
com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=PojoLinkInformatica, portType={
http://openesb.glassfish.org/InformaticaPOJOProvider/}InformaticaPOJOProviderInterface, operation=InformaticaPOJOProviderOperation)
BPCOR-6129:Line Number is 34

BPCOR-6130:Activity Name is Invoke1

       at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:974)

       at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:547)

       at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:182)

       at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:147)

       at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)

       at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1046)

       at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:278)

       at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1293)

       at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:402)

       at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)

       at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)

Caused by: java.lang.NullPointerException

       at org.glassfish.openesb.InformaticaPOJOProvider.receive(InformaticaPOJOProvider.java:99)

       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 org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor.executePojoOperation(InOutExecutor.java:76)

       at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.executePojoOperation(InMsgTask.java:231)

       at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.run(InMsgTask.java:116)

       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)

       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)

       at java.lang.Thread.run(Thread.java:619)

|#]


[#|2009-10-26T16:09:43.060-0700|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=53;_ThreadName=httpWorkerThread-4848-3;|Stopping service assembly CaInformatica on target server.|#]



Regards,
Saurabh Saxena

*IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. *

*IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. *

Girish Patil-2

Re: Unable to load jar to netbean 6.1 - pojo program

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)
From the logs it looks like "org.glassfish.openesb.InformaticaPOJOProvider"  is a POJO SE Service class developed by the user.

Do you know on what Jars it depends? If so you can create a Netbeans Java library and add that library to your Java SE project, so that all the lib jars will be packaged in POJO SE service unit and used during the runtime.

Does third party jars (guessing might be SAP Conversion Agent by Informatica) depend on any DLL?  If so does it run in standalone mode?

-Girish

Saurabh K Saxena wrote:

I put this jar file in all possible lib directories for java1.6, glassfish app server.

Here is our java.library.path from my windows xp desktop -
C:\Program Files\Informatica\DataTransformation\api\lib;C:\Program Files\Informatica\DataTransformation\bin;C:\JavaCAPS6\appserver\lib;C:\JavaCAPS6\appserver\bin|#]


Still getting that exception -
The shared object / DLL CM_JavaAPI could not be loaded. This could be the result of a problematic installation, a wrong library search path, or an attempt to load a 32/64-bit library from a 64/32-bit process. Operating System error message: no CM_JavaAPI in java.library.path!|#]




Regards,
Saurabh S,   RITS CDX /EDI /TM,   desk:  (206) 332-5957


From: "Saurabh K Saxena" [hidden email]
To: [hidden email]
Date: 10/26/2009 11:32 PM
Subject: Unable to load jar to netbean 6.1 - pojo program






I uploaded jar file in libraries and at run time it is unable to find this jar file and throwing this error. I am using JCAPS 6U1(Open ESB, JBI), POJO, BPEL and Composite Application. Kindly advice.


[#|2009-10-26T16:07:25.590-0700|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=51;_ThreadName=pojo-se-1;POJO Provider Class=class org.glassfish.openesb.InformaticaPOJOProvider;ServiceUnit=CaInformatica-jseInformaticaInterface;_RequestID=30e8bd9e-d10e-42b7-9b2e-ad9708cae387;|

<status><severity>4</severity><description>!The shared object / DLL CM_JavaAPI could not be loaded. This could be the result of a problematic installation, a wrong library search path, or an attempt to load a 32/64-bit library from a 64/32-bit process. Operating System error message: no CM_JavaAPI in java.library.path!</description></status>|#]


[#|2009-10-26T16:07:25.606-0700|SEVERE|sun-appserver9.1|org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor|_ThreadID=51;_ThreadName=pojo-se-1;POJO Provider Class=class org.glassfish.openesb.InformaticaPOJOProvider;ServiceUnit=CaInformatica-jseInformaticaInterface;_RequestID=30e8bd9e-d10e-42b7-9b2e-ad9708cae387;|The log message is null.

java.lang.NullPointerException

       at org.glassfish.openesb.InformaticaPOJOProvider.receive(InformaticaPOJOProvider.java:99)

       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 org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor.executePojoOperation(InOutExecutor.java:76)

       at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.executePojoOperation(InMsgTask.java:231)

       at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.run(InMsgTask.java:116)

       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)

       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)

       at java.lang.Thread.run(Thread.java:619)

|#]


[#|2009-10-26T16:07:25.621-0700|WARNING|sun-appserver9.1|com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl|_ThreadID=52;_ThreadName=BPELSEInOutThread9;Process Instance Id=10.24.10.42:49253bbf:1249317c5fe:-7fe7;Service Assembly Name=CaInformatica;BPEL Process Name=BpelInformaticaInterface;_RequestID=5f82058c-5091-45c0-a9aa-627e845c9cf9;|BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {
http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>null</jbi:part></jbi:message>
com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=PojoLinkInformatica, portType={
http://openesb.glassfish.org/InformaticaPOJOProvider/}InformaticaPOJOProviderInterface, operation=InformaticaPOJOProviderOperation)
BPCOR-6129:Line Number is 34

BPCOR-6130:Activity Name is Invoke1

       at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:974)

       at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:547)

       at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:182)

       at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:147)

       at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)

       at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1046)

       at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:278)

       at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1293)

       at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:402)

       at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)

       at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)

Caused by: java.lang.NullPointerException

       at org.glassfish.openesb.InformaticaPOJOProvider.receive(InformaticaPOJOProvider.java:99)

       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 org.glassfish.openesb.pojose.jbi.nmr.InOutExecutor.executePojoOperation(InOutExecutor.java:76)

       at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.executePojoOperation(InMsgTask.java:231)

       at org.glassfish.openesb.pojose.jbi.thread.InMsgTask.run(InMsgTask.java:116)

       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)

       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)

       at java.lang.Thread.run(Thread.java:619)

|#]


[#|2009-10-26T16:09:43.060-0700|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=53;_ThreadName=httpWorkerThread-4848-3;|Stopping service assembly CaInformatica on target server.|#]



Regards,
Saurabh Saxena

*IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. *

*IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. *