[Issue 1284] New - WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

View: New views
15 Messages — Rating Filter:   Alert me  

[Issue 1284] New - WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284
                 Issue #|1284
                 Summary|WS-TX Functional SQE tests are failing w/Metro 2.0 on
                        |GFv3
               Component|wsit
                 Version|2.0
                Platform|Macintosh
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|transaction
             Assigned to|m_potociar
             Reported by|m_potociar






------- Additional comments from m_potociar@... Wed Oct 14 12:07:39 +0000 2009 -------
Assuming that all WS-TX issues on GFv3 are caused by the same set of reasons, I
am opening this issue as a common umbrella issue for WS-TX issues #1090, #1091,
#1099, #1228, #1229, #1230. I am also going to close those six separate issues
as duplicates of this one.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from m_potociar@... Wed Oct 14 12:13:05 +0000 2009 -------
*** Issue 1090 has been marked as a duplicate of this issue. ***

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284



User m_potociar changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |STARTED
--------------------------------------------------------------------------------
        Target milestone|not determined            |2.0
--------------------------------------------------------------------------------




------- Additional comments from m_potociar@... Wed Oct 14 12:21:39 +0000 2009 -------
Before running the tests, please try these workarounds on GFv3 setup:

1. Manually deploy wstx-services.war to each GFv3 domain under the context root
"__wstx-services"

2. Make sure that HTTPS is enabled in the GFv3 domain's domain.xml config file

3. If the tests still fail, check if you can see the following warning message
in the server log:
"WSTX-COMMON-2015: Failed to get the FQDN and secure and non-secure http
listener ports from AS, falling back to <some-address-and-port>"

If you can see the message, and the fallback address and port don't correspond
to the actual domain's configuration, then try to add the following JVM argument
to the GFv3 domain startup options (in domain.xml config file):

<jvm-options>-Dcom.sun.xml.ws.tx.httpsPortOverride=XXXX</jvm-options>

where XXXX value should be set to the proper value of domain's HTTPS port (the
default is 8181)





---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from m_potociar@... Wed Oct 14 12:22:35 +0000 2009 -------
*** Issue 1091 has been marked as a duplicate of this issue. ***

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from m_potociar@... Wed Oct 14 12:24:33 +0000 2009 -------
*** Issue 1099 has been marked as a duplicate of this issue. ***

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284



User m_potociar changed the following:

                What    |Old value                 |New value
================================================================================
             Assigned to|m_potociar                |jbenoit
--------------------------------------------------------------------------------
                  Status|STARTED                   |NEW
--------------------------------------------------------------------------------




------- Additional comments from m_potociar@... Wed Oct 14 12:24:49 +0000 2009 -------
Assigning to QA contact: Please try the suggested workaround and rerun the
functional WSTX SQE tests

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from m_potociar@... Wed Oct 14 12:26:16 +0000 2009 -------
*** Issue 1228 has been marked as a duplicate of this issue. ***

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from m_potociar@... Wed Oct 14 12:26:59 +0000 2009 -------
*** Issue 1229 has been marked as a duplicate of this issue. ***

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from m_potociar@... Wed Oct 14 12:27:30 +0000 2009 -------
*** Issue 1230 has been marked as a duplicate of this issue. ***

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284



User m_potociar changed the following:

                What    |Old value                 |New value
================================================================================
                Keywords|                          |metro2.0-waived
--------------------------------------------------------------------------------




------- Additional comments from m_potociar@... Thu Oct 29 11:32:25 +0000 2009 -------
waiving this issue for Metro 2.0 release

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by jbenoit :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from jbenoit@... Sat Nov  7 04:30:21 +0000 2009 -------
regarding:

"Before running the tests, please try these workarounds on GFv3 setup:

1. Manually deploy wstx-services.war to each GFv3 domain under the context root
"__wstx-services" "

exactly how do we do this step?  i don't see wstx-services.war under GF V3
installation, where does this file reside?  once it's located, how do i
"manually deploy to each GFv3 domains under context root __wstx-services"?  do i
edit domain.xml and add something, or do i copy .war file to some autodeploy
directory? or do i use admin gui, or....?  please advise on specifics on how to
do this?

> 2. Make sure that HTTPS is enabled in the GFv3 domain's domain.xml config file

exactly how do i ensure that https is enabled?  do i search for https and look
for enabled="true" or some such method?

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by jbenoit :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from jbenoit@... Sat Nov  7 04:32:01 +0000 2009 -------
i found wstx-services.war in metro binary under metro/lib/wstx-services.war.  do
i have to install all of metro on top of GF V3 installation?  or do i just have
to get this file deployed as you describe without installing all of metro on top
of GF V3?

please clarify.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from m_potociar@... Sat Nov  7 22:53:45 +0000 2009 -------
Only the wstx-services.war needs to be deployed. That's the only missing part.
To deploy it, you can use admin console (or any other way of deploying a web
application to GF).

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by jbenoit :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from jbenoit@... Thu Nov 12 04:05:54 +0000 2009 -------
metro/lib/wstx-services.war sun-web.xml file entry:

    <context-root>t</context-root>

should be:

 <context-root>__wstx-services</context-root>

so that when wstx-services.war is copied to AS_HOME/domains/domain1/autodeploy/
directory the server.log is populated with output that corresponds to .war being
deployed with proper context root instead of seeing this:

[#|2009-11-11T22:14:57.243-0500|INFO|glassfishv3.0|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=24;_ThreadName=Thread-1;|[AutoDeploy]
Selecting file
/net/galapago.east/files/share/workspaces/gfv3metro20/glassfishv3/glassfish/domains/domain1/autodeploy/wstx-services.war
for autodeployment.|#]

[#|2009-11-11T22:14:59.853-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 CompletionCoordinatorPortTypeImpl  listening at address at
http://localhost:8080/t/wsat/completion/coordinator|#]

[#|2009-11-11T22:14:59.857-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 ActivationRequesterPortTypeImpl  listening at address at
http://localhost:8080/t/wscoor/coordinator/createCoordinationContextResponse|#]

[#|2009-11-11T22:14:59.861-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 CompletionInitiatorPortTypeImpl  listening at address at
http://localhost:8080/t/wsat/completion/initiator|#]

[#|2009-11-11T22:14:59.865-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 CoordinatorPortTypeImpl  listening at address at
http://localhost:8080/t/wsat/coordinator|#]

[#|2009-11-11T22:14:59.869-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 ParticipantPortTypeImpl  listening at address at
http://localhost:8080/t/wsat/2pc|#]

[#|2009-11-11T22:14:59.873-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 RegistrationRequesterPortTypeImpl  listening at address at
http://localhost:8080/t/wscoor/coordinator/registerResponse|#]

[#|2009-11-11T22:14:59.877-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 RegistrationPortTypeImpl  listening at address at
http://localhost:8080/t/wscoor/coordinator/synchRegister|#]

[#|2009-11-11T22:14:59.882-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 ActivationCoordinatorPortTypeImpl  listening at address at
http://localhost:8080/t/wscoor/coordinator/createCoordinationContext|#]

[#|2009-11-11T22:14:59.886-0500|INFO|glassfishv3.0|javax.enterprise.webservices.org.glassfish.webservices|_ThreadID=24;_ThreadName=Thread-1;|WS00018:
Webservice Endpoint deployed
 RegistrationCoordinatorPortTypeImpl  listening at address at
http://localhost:8080/t/wscoor/coordinator/register|#]

[#|2009-11-11T22:15:09.031-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-Coordinator-ActivationCoordinator|#]

[#|2009-11-11T22:15:13.262-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-Coordinator-ActivationRequester|#]

[#|2009-11-11T22:15:13.516-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-Coordinator-RegistrationCoordinator|#]

[#|2009-11-11T22:15:13.751-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-Coordinator-RegistrationRequester|#]

[#|2009-11-11T22:15:13.989-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-Coordinator-Registration|#]

[#|2009-11-11T22:15:14.229-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-WSATCoordinator-Coordinator|#]

[#|2009-11-11T22:15:14.407-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-WSATCoordinator-Participant|#]

[#|2009-11-11T22:15:14.581-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-WSATCoordinator-CompletionCoordinator|#]

[#|2009-11-11T22:15:14.715-0500|WARNING|glassfishv3.0|com.sun.xml.ws.model.JavaMethodImpl|_ThreadID=24;_ThreadName=Thread-1;|Input
Action on WSDL operation AbortedOperation and @Action on its associated Web
Method abortedOperation did not match and will cause problems in dispatching the
requests|#]

[#|2009-11-11T22:15:14.716-0500|WARNING|glassfishv3.0|com.sun.xml.ws.model.JavaMethodImpl|_ThreadID=24;_ThreadName=Thread-1;|Input
Action on WSDL operation CommittedOperation and @Action on its associated Web
Method committedOperation did not match and will cause problems in dispatching
the requests|#]

[#|2009-11-11T22:15:14.773-0500|INFO|glassfishv3.0|javax.enterprise.resource.webservices.jaxws.monitoring|_ThreadID=24;_ThreadName=Thread-1;|Metro
monitoring rootname successfully set to:
com.sun.metro:pp=/,type=WSEndpoint,name=/t-WSATCoordinator-CompletionInitiator|#]

[#|2009-11-11T22:15:14.851-0500|INFO|glassfishv3.0|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=24;_ThreadName=Thread-1;|Loading
application wstx-services at /t|#]



also, seeing these two warnings which should be fixed:

[#|2009-11-11T22:15:14.715-0500|WARNING|glassfishv3.0|com.sun.xml.ws.model.JavaMethodImpl|_ThreadID=24;_ThreadName=Thread-1;|Input
Action on WSDL operation AbortedOperation and @Action on its associated Web
Method abortedOperation did not match and will cause problems in dispatching the
requests|#]

[#|2009-11-11T22:15:14.716-0500|WARNING|glassfishv3.0|com.sun.xml.ws.model.JavaMethodImpl|_ThreadID=24;_ThreadName=Thread-1;|Input
Action on WSDL operation CommittedOperation and @Action on its associated Web
Method committedOperation did not match and will cause problems in dispatching
the requests|#]


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...


[Issue 1284] WS-TX Functional SQE tests are failing w/Metro 2.0 on GFv3

by m_potociar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://wsit.dev.java.net/issues/show_bug.cgi?id=1284






------- Additional comments from m_potociar@... Fri Nov 13 11:25:49 +0000 2009 -------
The context root has been fixed on the main trunk.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...