December 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1362) problem in deploying seam application

by Gaurav Gupta (JIRA)

Gaurav Gupta created JBTM-1362: ---------------------------------- Summary: problem in deploying seam application Key: JBTM-1362 URL: https://issues.jboss.org/browse/JBTM-1362 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gaurav Gupta Assignee: Tom Jenkinson 18:39:52,684 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://soap.sforce.com/2005/09/outbound}CoreWsImplService from class no.messageman.protectoria.core.salesforce.buyfromsalesman.outbound.CoreWsImpl 18:39:53,089 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/app/NotificationPort 18:39:53,179 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-3) WSDL published to: file:/D:/MM%20Venus%20Project/JBOSS/jboss-as-7.1.1.Final/standalone/data/wsdl/protectoria.ear/app.jar/CoreWsImplService.wsdl 18:39:53,200 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.port-component-link 18:39:53,266 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."protectoria.ear"."app.jar".CoreWsImpl 18:39:53,268 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.endpoint."protectoria.ear"."app.jar".ThickClientSharedSecretEncryptedWS 18:39:53,283 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=app,endpoint=CoreWsImpl 18:39:53,291 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-4) register: jboss.ws:context=app,endpoint=ThickClientSharedSecretEncryptedWS 18:39:53,508 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990 18:39:53,515 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 57864ms - Started 1491 of 1687 services (115 services failed or missing dependencies, 80 services are passive or on-demand) 18:39:53,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "protectoria.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"protectoria.ear/app.jar#protectoria\"jboss.naming.context.java.jboss.datasources.MySqlDSMissing[jboss.persistenceunit.\"protectoria.ear/app.jar#protectoria\"jboss.naming.context.java.jboss.datasources.MySqlDS]","jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".notificationSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.notification.mailMissing[jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".notificationSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.notification.mail]","jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".outboundSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.outbound.mailMissing[jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".outboundSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.outbound.mail]"]} 18:39:53,824 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.endpoint."protectoria.ear"."app.jar".CoreWsImpl 18:39:53,824 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."protectoria.ear"."app.jar".ThickClientSharedSecretEncryptedWS 18:39:53,837 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) remove: jboss.ws:context=app,endpoint=CoreWsImpl 18:39:53,853 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=app,endpoint=ThickClientSharedSecretEncryptedWS 18:39:53,978 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.port-component-link 18:39:54,207 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment app.jar in 492ms 18:39:54,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment app.war in 545ms 18:39:54,372 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment protectoria.ear in 657ms 18:39:54,381 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.naming.context.java.comp.protectoria."app.jar".SMTPHandler.env.protectoria.notification.mail (missing) dependents: [service jboss.naming.context.java.comp.protectoria."app.jar".SMTPHandler.env."no.messageman.protectoria.core.smtp.SMTPHandler".notificationSession] service jboss.naming.context.java.comp.protectoria."app.jar".SMTPHandler.env.protectoria.outbound.mail (missing) dependents: [service jboss.naming.context.java.comp.protectoria."app.jar".SMTPHandler.env."no.messageman.protectoria.core.smtp.SMTPHandler".outboundSession] service jboss.naming.context.java.jboss.datasources.MySqlDS (missing) dependents: [service jboss.persistenceunit."protectoria.ear/app.jar#protectoria"] 18:39:54,447 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"protectoria.ear/app.jar#protectoria\"jboss.naming.context.java.jboss.datasources.MySqlDSMissing[jboss.persistenceunit.\"protectoria.ear/app.jar#protectoria\"jboss.naming.context.java.jboss.datasources.MySqlDS]","jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".notificationSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.notification.mailMissing[jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".notificationSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.notification.mail]","jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".outboundSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.outbound.mailMissing[jboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.\"no.messageman.protectoria.core.smtp.SMTPHandler\".outboundSessionjboss.naming.context.java.comp.protectoria.\"app.jar\".SMTPHandler.env.protectoria.outbound.mail]"]}}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

[JBoss JIRA] (JBTM-1337) Use the node name if it is set, rather than the host name to construct Uid

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1337: ----------------------------------- Summary: Use the node name if it is set, rather than the host name to construct Uid Key: JBTM-1337 URL: https://issues.jboss.org/browse/JBTM-1337 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Node name is going to give us guaranteed uniqueness for transaction managers, we could use node name instead of hostname and pid. Uid is generic, xa node name is part of XA, but they are both in ArjunaCore/arjuna/ so it should not pose any dependency issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
5
0 / 0

[JBoss JIRA] (JBTM-1336) DUPID detection for mysql in JTS mode does not work

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1336: ----------------------------------- Summary: DUPID detection for mysql in JTS mode does not work Key: JBTM-1336 URL: https://issues.jboss.org/browse/JBTM-1336 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.16.7, 5.0.0.M2, 4.17.3 Mysql does not send errorcode of XAException.XAER_DUPID, it sends 0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
6
0 / 0

[JBoss JIRA] (JBTM-1182) Provide an rpm for Narayana

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1182: ----------------------------------- Summary: Provide an rpm for Narayana Key: JBTM-1182 URL: https://issues.jboss.org/browse/JBTM-1182 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.1.Final Especially now we have transactional file i/o -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
1
0 / 0

[JBoss JIRA] (JBTM-1081) Consider adding photos and bios to the team page

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1081: ----------------------------------- Summary: Consider adding photos and bios to the team page Key: JBTM-1081 URL: https://issues.jboss.org/browse/JBTM-1081 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Tom Jenkinson Fix For: 5.0.0.Final I really like the HornetQ team page: http://www.jboss.org/hornetq/community/team.html I think having photos and bios makes us more approachable to the community. Also the bios should instil confidence that the project is in good hands. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
7
0 / 0

[JBoss JIRA] (JBTM-1164) Google+ release annoucements

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1164: ----------------------------------- Summary: Google+ release annoucements Key: JBTM-1164 URL: https://issues.jboss.org/browse/JBTM-1164 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-846) Remove static initializers

by Tom Jenkinson (JIRA)

Remove static initializers -------------------------- Key: JBTM-846 URL: https://issues.jboss.org/browse/JBTM-846 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
5
0 / 0

[JBoss JIRA] (JBTM-1227) StAX is not available on Android

by Mark Little (JIRA)

Mark Little created JBTM-1227: --------------------------------- Summary: StAX is not available on Android Key: JBTM-1227 URL: https://issues.jboss.org/browse/JBTM-1227 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common Affects Versions: 5.0.0.M1, 4.16.4 Environment: Android 2.3.3 Reporter: Mark Little Assignee: Tom Jenkinson StAX is not available. Since we use it for property configuration, the system fails to run unmodified. There is an equivalent implementation (XmlPullParser) but it is likely other JBoss projects will suffer from this issue. See http://www.ibm.com/developerworks/library/x-android/ for more details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

[JBoss JIRA] (JBTM-1045) Add a persistent object into the recovery manager that we can talk to in the event of ONE after a resource has completed

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1045: ----------------------------------- Summary: Add a persistent object into the recovery manager that we can talk to in the event of ONE after a resource has completed Key: JBTM-1045 URL: https://issues.jboss.org/browse/JBTM-1045 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M2 add a persistent IOR into the RecoveryManager and that's used in the event we get the ONE for a basic resource. Kind of like a reverse RecoveryCoordinator (top-down RecoveryCoordinator) You can embed lots of information into an IOR, so we can do this without changing any interfaces. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
4
0 / 0

[JBoss JIRA] (JBTM-17) Rebadge existing Arjuna Transaction Service training material

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-17?page=com.atlassian.jira.plugin.sy... ] Tom Jenkinson resolved JBTM-17. ------------------------------- Fix Version/s: 4.16.5 (was: 5.0.0.Final) Resolution: Done Training on 4.16.5 already delivered: https://svn.devel.redhat.com/repos/jbossts/trunk/training/for_inhouse_sup... > Rebadge existing Arjuna Transaction Service training material > ------------------------------------------------------------- > > Key: JBTM-17 > URL: https://issues.jboss.org/browse/JBTM-17 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA, JTS, XTS > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 4.16.5 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Re-badge training material and collateral (presentations, white papers, etc.) Currently docs are distributed in pdf format. Is this a problem? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2012