Issue Details (XML | Word | Printable)

Key: GLASSFISH-18858
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: marina vatkina
Reporter: aelena
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

After the execution of versioning timer apps deployment, next timer apps deployment - failed.

Created: 29/Jun/12 07:01 PM   Updated: 16/Aug/12 04:36 PM   Resolved: 16/Aug/12 04:36 PM
Component/s: ejb_container
Affects Version/s: 4.0_b43
Fix Version/s: 4.0_b50_ms4

Time Tracking:
Not Specified

File Attachments: 1. XML File domain.xml (57 kB) 29/Jun/12 11:49 PM - aelena
2. File setup_cl.pl (1 kB) 05/Jul/12 06:24 PM - aelena
3. Text File timer.log (43 kB) 29/Jun/12 07:01 PM - aelena
4. File workaround.sh (0.4 kB) 05/Jul/12 06:24 PM - aelena


Tags: 40-regression
Participants: aelena, Alex Pineda, Hong Zhang and marina vatkina


 Description  « Hide

Promoted 4.0 build 43. OEL6 or Solaris Sparc 10.

Created a cluster with two instances.

The deployment of all timer apps to the cluster failed.

It happened if before were executed the follow timer app deployment commands:
asadmin deploy --target domain --name=timersession:1.0 --retrieve /opt/appserver-sqe/pe/deploymen
t_v3 /opt/appserver-sqe/pe/deployment_v3/archives_nodb/timersession.ear

asadmin deploy --target my-c1 --name=timersession:1.0 --retrieve /opt/appserver-sqe/pe/deployment
_v3 /opt/appserver-sqe/pe/deployment_v3/archives_nodb/timersession.ear

(The second deployment created syntax warning, see bug: 18857)

Then the apps were undeployed; cluster and instances were removed, recreated and started; DB restarted; domain restarted; all required resources recreated.

After that was executed the follow depoyment command:

asadmin deploy --target my-c1 /opt/appserver-sqe/pe/deployment_v3/archives_nodb/timersession.ear

This deployment and the deployment of all other timer apps - failed. I've attached the correspondent error messages from server.log.

If these two first versioning timer app deployment would not be executed, then the next timer apps deployment would not fail.

This is a regression issue, for example, this issue was not seen for b35.



Sort Order: Ascending order - Click to sort in descending order
aelena made changes - 29/Jun/12 11:49 PM
Field Original Value New Value
Attachment domain.xml [ 50455 ]
Hong Zhang made changes - 05/Jul/12 03:31 PM
Assignee Hong Zhang [ hzhang_jn ] marina vatkina [ mvatkina ]
Component/s ejb_container [ 10596 ]
Component/s deployment [ 10594 ]
marina vatkina made changes - 05/Jul/12 04:34 PM
Assignee marina vatkina [ mvatkina ] Hong Zhang [ hzhang_jn ]
Component/s deployment [ 10594 ]
Component/s ejb_container [ 10596 ]
aelena made changes - 05/Jul/12 06:24 PM
Attachment workaround.sh [ 50491 ]
Attachment setup_cl.pl [ 50492 ]
Alex Pineda made changes - 12/Jul/12 05:07 AM
Tags 40-regression
Hong Zhang made changes - 02/Aug/12 03:01 PM
Assignee Hong Zhang [ hzhang_jn ] marina vatkina [ mvatkina ]
Component/s ejb_container [ 10596 ]
Component/s deployment [ 10594 ]
marina vatkina made changes - 16/Aug/12 04:36 PM
Status Open [ 1 ] Resolved [ 5 ]
Fix Version/s 4.0_b50_ms4 [ 15639 ]
Resolution Fixed [ 1 ]