You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "shrikant (JIRA)" <ji...@apache.org> on 2008/07/31 03:18:31 UTC
[jira] Created: (RAMPART-188) unable to engage rampart 1.4 on
websphere application server 6.1
unable to engage rampart 1.4 on websphere application server 6.1
----------------------------------------------------------------
Key: RAMPART-188
URL: https://issues.apache.org/jira/browse/RAMPART-188
Project: Rampart
Issue Type: Bug
Components: rampart-core, rampart-integration, rampart-policy, rampart-trust
Affects Versions: 1.4
Environment: websphere application server 6.1.
Reporter: shrikant
Assignee: Ruchith Udayanga Fernando
Priority: Blocker
I have enterprise app which contains a MDB and a web service client (java project) on websphere 6.1. I am using axis2 1.4 jars, rampart 1.4 for client project. When the mdb invokes the web service client, I am exception AxisFault: Trying to engage a module which is not available: rampart.
I am able to run the web service client in standalone mode, but when it is packaged and deployed within EAR its not able to engage the rampart module. However axis is able to engage the addressing module perfectly fine.
I have configured my application class loader policy as "parent last" to make sure that apps jars are loaded first.
I do not know why rampart module is not being engaged when the web service client application is deployed onto websphere application server 6.1. Any help will be appreciated.
Thank you,
Shrikant
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RAMPART-188) unable to engage rampart 1.4 on
websphere application server 6.1
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720025#action_12720025 ]
Nandana Mihindukulasooriya commented on RAMPART-188:
----------------------------------------------------
Most common reason for this is not having Rampart and its dependency jars in the classpath. Can you please check three Rampart jars and its dependencies available in client classpath ?
thanks,
Nandana
> unable to engage rampart 1.4 on websphere application server 6.1
> ----------------------------------------------------------------
>
> Key: RAMPART-188
> URL: https://issues.apache.org/jira/browse/RAMPART-188
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core, rampart-integration, rampart-policy, rampart-trust
> Affects Versions: 1.4
> Environment: websphere application server 6.1.
> Reporter: shrikant
> Assignee: Ruchith Udayanga Fernando
> Priority: Blocker
> Original Estimate: 32h
> Remaining Estimate: 32h
>
> I have enterprise app which contains a MDB and a web service client (java project) on websphere 6.1. I am using axis2 1.4 jars, rampart 1.4 for client project. When the mdb invokes the web service client, I am exception AxisFault: Trying to engage a module which is not available: rampart.
> I am able to run the web service client in standalone mode, but when it is packaged and deployed within EAR its not able to engage the rampart module. However axis is able to engage the addressing module perfectly fine.
> I have configured my application class loader policy as "parent last" to make sure that apps jars are loaded first.
> I do not know why rampart module is not being engaged when the web service client application is deployed onto websphere application server 6.1. Any help will be appreciated.
> Thank you,
> Shrikant
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RAMPART-188) unable to engage rampart 1.4 on
websphere application server 6.1
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738859#action_12738859 ]
Nandana Mihindukulasooriya commented on RAMPART-188:
----------------------------------------------------
Hi Shrikant,
Do you have any update on this issue ?
regards,
Nandana
> unable to engage rampart 1.4 on websphere application server 6.1
> ----------------------------------------------------------------
>
> Key: RAMPART-188
> URL: https://issues.apache.org/jira/browse/RAMPART-188
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core, rampart-integration, rampart-policy, rampart-trust
> Affects Versions: 1.4
> Environment: websphere application server 6.1.
> Reporter: shrikant
> Assignee: Ruchith Udayanga Fernando
> Priority: Blocker
> Original Estimate: 32h
> Remaining Estimate: 32h
>
> I have enterprise app which contains a MDB and a web service client (java project) on websphere 6.1. I am using axis2 1.4 jars, rampart 1.4 for client project. When the mdb invokes the web service client, I am exception AxisFault: Trying to engage a module which is not available: rampart.
> I am able to run the web service client in standalone mode, but when it is packaged and deployed within EAR its not able to engage the rampart module. However axis is able to engage the addressing module perfectly fine.
> I have configured my application class loader policy as "parent last" to make sure that apps jars are loaded first.
> I do not know why rampart module is not being engaged when the web service client application is deployed onto websphere application server 6.1. Any help will be appreciated.
> Thank you,
> Shrikant
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPART-188) unable to engage rampart 1.4 on
websphere application server 6.1
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya updated RAMPART-188:
-----------------------------------------------
Priority: Major (was: Blocker)
Lowering the priority as this is not a blocker.
> unable to engage rampart 1.4 on websphere application server 6.1
> ----------------------------------------------------------------
>
> Key: RAMPART-188
> URL: https://issues.apache.org/jira/browse/RAMPART-188
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core, rampart-integration, rampart-policy, rampart-trust
> Affects Versions: 1.4
> Environment: websphere application server 6.1.
> Reporter: shrikant
> Assignee: Ruchith Udayanga Fernando
> Original Estimate: 32h
> Remaining Estimate: 32h
>
> I have enterprise app which contains a MDB and a web service client (java project) on websphere 6.1. I am using axis2 1.4 jars, rampart 1.4 for client project. When the mdb invokes the web service client, I am exception AxisFault: Trying to engage a module which is not available: rampart.
> I am able to run the web service client in standalone mode, but when it is packaged and deployed within EAR its not able to engage the rampart module. However axis is able to engage the addressing module perfectly fine.
> I have configured my application class loader policy as "parent last" to make sure that apps jars are loaded first.
> I do not know why rampart module is not being engaged when the web service client application is deployed onto websphere application server 6.1. Any help will be appreciated.
> Thank you,
> Shrikant
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.