[JBoss JIRA] (JBESB-3917) DB schema upgrade support
by Andrew Matusevich (JIRA)
[ https://issues.jboss.org/browse/JBESB-3917?page=com.atlassian.jira.plugin... ]
Andrew Matusevich updated JBESB-3917:
-------------------------------------
Description:
Currently ESB does not support seamless migration for messaging/registry persistence DB schema/data when ESB version is upgraded.
Customer encountered errors when migrating from SOA-P 3.5.0 => 3.5.1
Expectation is that ESB should upgrade DB tables without loosing any data at start-up, they cannot afford starting with fresh schema in production environment as they may have messages in flight etc
was:
Currently ESB does not support seamless migration for messaging/registry persistence DB schema/data when ESB version is upgraded.
Customer encountered errors when migrating from SOA-P 3.5.0 => 3.5.1
Expectation is that ESB should upgrade DB tables without loosing any data at start-up, they cannot afford starting with fresh schema in production environment as they may have messages in flight etc
Account: YellowBook (479353)
TAM customer: yes
SRM customer: yes
Strategic: yes
> DB schema upgrade support
> -------------------------
>
> Key: JBESB-3917
> URL: https://issues.jboss.org/browse/JBESB-3917
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Deployment
> Affects Versions: 4.11
> Reporter: Andrew Matusevich
>
> Currently ESB does not support seamless migration for messaging/registry persistence DB schema/data when ESB version is upgraded.
> Customer encountered errors when migrating from SOA-P 3.5.0 => 3.5.1
> Expectation is that ESB should upgrade DB tables without loosing any data at start-up, they cannot afford starting with fresh schema in production environment as they may have messages in flight etc
--
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
11 years
[JBoss JIRA] (JBESB-3917) DB schema upgrade support
by Andrew Matusevich (JIRA)
Andrew Matusevich created JBESB-3917:
----------------------------------------
Summary: DB schema upgrade support
Key: JBESB-3917
URL: https://issues.jboss.org/browse/JBESB-3917
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 4.11
Reporter: Andrew Matusevich
Currently ESB does not support seamless migration for messaging/registry persistence DB schema/data when ESB version is upgraded.
Customer encountered errors when migrating from SOA-P 3.5.0 => 3.5.1
Expectation is that ESB should upgrade DB tables without loosing any data at start-up, they cannot afford starting with fresh schema in production environment as they may have messages in flight etc
Account: YellowBook (479353)
TAM customer: yes
SRM customer: yes
Strategic: yes
--
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
11 years
[JBoss JIRA] (JBESB-3587) Enabling xslt parameters support in XsltAction
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3587?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato reassigned JBESB-3587:
-------------------------------------
Assignee: Tadayoshi Sato
> Enabling xslt parameters support in XsltAction
> ----------------------------------------------
>
> Key: JBESB-3587
> URL: https://issues.jboss.org/browse/JBESB-3587
> Project: JBoss ESB
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Transformation Service
> Affects Versions: 4.9
> Environment: Linux
> Reporter: Eduardo de Vera Toquero
> Assignee: Tadayoshi Sato
> Labels: configuration, parameters, xslt:param, xsltAction
> Fix For: 4.13
>
> Attachments: xslt-param-patch.txt
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Enhancement of xslt parameters in order to be able to pass values to xslt parameters on the xslt action. Ideally, using prefixes, one could chose whether to pass a value located at the configuration file (ConfigTree) or from the ESB Message. Values need to be stringed.
--
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
11 years
[JBoss JIRA] (JBESB-3916) JBoss ESB 4.11, 4.12 generates hibernate error on JBoss AS 5.1.0.GA out of the box
by Ian Walker (JIRA)
Ian Walker created JBESB-3916:
---------------------------------
Summary: JBoss ESB 4.11, 4.12 generates hibernate error on JBoss AS 5.1.0.GA out of the box
Key: JBESB-3916
URL: https://issues.jboss.org/browse/JBESB-3916
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Application Server, Configuration
Affects Versions: 4.12, 4.11
Environment: RedHat Enterprise Linux 6.2 64-bit, OpenJDK 1.6.0_22, JBoss AS 5.1.0.Final
Windows XP 32-bit, Oracle JDK 1.6.0_43, JBoss AS 5.1.0.Final
Reporter: Ian Walker
When running JBoss ESB 4.11, or 4.12 in JBoss AS 5.1.0.GA, after server starts up the following error is continually logged:
{noformat}
16:29:56,867 INFO [Configuration] configuring from resource: hibernate.cfg.xml
16:29:56,867 INFO [Configuration] Configuration resource: hibernate.cfg.xml
16:29:56,869 DEBUG [DTDEntityResolver] trying to resolve system-id [http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd]
16:29:56,869 DEBUG [DispatcherThread] failed to retrieve next waiting due job
org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1528)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1462)
at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
at org.jbpm.svc.Services.getService(Services.java:160)
at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
at org.jbpm.job.executor.DispatcherThread.getNextDueDateWithinIdleInterval(DispatcherThread.java:193)
at org.jbpm.job.executor.DispatcherThread.run(DispatcherThread.java:70)
Caused by: org.dom4j.DocumentException: www.hibernate.org Nested exception: www.hibernate.org
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1518)
{noformat}
Problem appears to be caused by a mismatch with the DTD name in the {{deploy/jbpm.esb/hibernate.cfg.xml}} and {{hibernate-core.jar/hibernate-configuration-3.0.dtd}}.
{{hibernate.cfg.xml}} uses the following:
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd">
{code}
However, the {{hibernate-configuration-3.0.dtd}} uses {{http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd}}.
Changing {{hibernate.cfg.xml}} to use the above URL fixes the errors for JBoss AS 5.1.0.GA.
JBoss AS 6.1.0.Final has no problem. The {{hibernate-configuration-3.0.dtd}} in AS6 uses the www.hibernate.org address.
--
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
11 years, 1 month
[JBoss JIRA] (JBESB-3816) Get an HibernateException in JbpmJobExector when starting 4.11 out of the box
by Ian Walker (JIRA)
[ https://issues.jboss.org/browse/JBESB-3816?page=com.atlassian.jira.plugin... ]
Ian Walker edited comment on JBESB-3816 at 4/5/13 3:58 AM:
-----------------------------------------------------------
Just installed JBoss AS 5.1.0.GA + JBoss ESB 4.12 on RHEL 6.2 and got the same Hibernate error. Running with debug logging turned on, I get the following:
{noformat}
16:29:56,867 INFO [Configuration] configuring from resource: hibernate.cfg.xml
16:29:56,867 INFO [Configuration] Configuration resource: hibernate.cfg.xml
16:29:56,869 DEBUG [DTDEntityResolver] trying to resolve system-id [http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd]
16:29:56,869 DEBUG [DispatcherThread] failed to retrieve next waiting due job
org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1528)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1462)
at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
at org.jbpm.svc.Services.getService(Services.java:160)
at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
at org.jbpm.job.executor.DispatcherThread.getNextDueDateWithinIdleInterval(DispatcherThread.java:193)
at org.jbpm.job.executor.DispatcherThread.run(DispatcherThread.java:70)
Caused by: org.dom4j.DocumentException: www.hibernate.org Nested exception: www.hibernate.org
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1518)
{noformat}
Looking through the installed JBoss ESB 4.12, I found {{www.hibernate.com...}} in the {{deploy/jbpm.esb/hibernate.cfg.xml}}.
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd">
{code}
Changing {{hibernate.cfg.xml}} to the following (taken from ESB 4.10) seems to fix the problem on both RHEL and Windows.
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
{code}
was (Author: ian.walker):
Just installed JBoss AS 5.1.0.GA + JBoss ESB 4.12 on RHEL 6.2 and got the same Hiberate error. Running with debug logging turned on, I get the following:
{noformat}
16:29:56,867 INFO [Configuration] configuring from resource: hibernate.cfg.xml
16:29:56,867 INFO [Configuration] Configuration resource: hibernate.cfg.xml
16:29:56,869 DEBUG [DTDEntityResolver] trying to resolve system-id [http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd]
16:29:56,869 DEBUG [DispatcherThread] failed to retrieve next waiting due job
org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1528)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1462)
at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
at org.jbpm.svc.Services.getService(Services.java:160)
at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
at org.jbpm.job.executor.DispatcherThread.getNextDueDateWithinIdleInterval(DispatcherThread.java:193)
at org.jbpm.job.executor.DispatcherThread.run(DispatcherThread.java:70)
Caused by: org.dom4j.DocumentException: www.hibernate.org Nested exception: www.hibernate.org
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1518)
{noformat}
Looking through the installed JBoss ESB 4.12, I found {{www.hibernate.com...}} in the {{deploy/jbpm.esb/hibernate.cfg.xml}}.
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd">
{code}
Changing {{hibernate.cfg.xml}} to the following (taken from ESB 4.10) seems to fix the problem on both RHEL and Windows.
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
{code}
> Get an HibernateException in JbpmJobExector when starting 4.11 out of the box
> -----------------------------------------------------------------------------
>
> Key: JBESB-3816
> URL: https://issues.jboss.org/browse/JBESB-3816
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Deployment
> Affects Versions: 4.11
> Environment: Windows 7
> Reporter: Olle Sundblad
>
> When I download and install (unzip) the 4.11 release and start it using run.bat without any changes whatsoever I get the following stacktrace over and over again.
> end of start console (it started with no errors/warnings):
> 09:57:16,666 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
> 09:57:16,677 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 28s:270ms
> but immediately after I get the following:
> 09:57:31,928 INFO [Configuration] configuring from resource: hibernate.cfg.xml
> 09:57:31,929 INFO [Configuration] Configuration resource: hibernate.cfg.xml
> 09:57:52,939 INFO [Configuration] configuring from resource: hibernate.cfg.xml
> 09:57:52,940 INFO [Configuration] Configuration resource: hibernate.cfg.xml
> 09:57:52,939 ERROR [LockMonitorThread] exception in JbpmJobExector@138.106.178.133:Monitor
> org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1494)
> at org.hibernate.cfg.Configuration.configure(Configuration.java:1428)
> at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
> at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
> at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
> at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
> at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
> at org.jbpm.svc.Services.getService(Services.java:160)
> at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
> at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
> at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
> at org.jbpm.job.executor.LockMonitorThread.unlockOverdueJobs(LockMonitorThread.java:64)
> at org.jbpm.job.executor.LockMonitorThread.run(LockMonitorThread.java:43)
> Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
> at org.dom4j.io.SAXReader.read(SAXReader.java:484)
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1484)
> ... 15 more
> This repeats over and over again until I stop the server.
> I do not get this exception in 4.10 (so my unqualified guess is the jbpm5 stuff is missing the hibernate.cfg.xml or something)
--
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
11 years, 1 month
[JBoss JIRA] (JBESB-3816) Get an HibernateException in JbpmJobExector when starting 4.11 out of the box
by Ian Walker (JIRA)
[ https://issues.jboss.org/browse/JBESB-3816?page=com.atlassian.jira.plugin... ]
Ian Walker commented on JBESB-3816:
-----------------------------------
Just installed JBoss AS 5.1.0.GA + JBoss ESB 4.12 on RHEL 6.2 and got the same Hiberate error. Running with debug logging turned on, I get the following:
{noformat}
16:29:56,867 INFO [Configuration] configuring from resource: hibernate.cfg.xml
16:29:56,867 INFO [Configuration] Configuration resource: hibernate.cfg.xml
16:29:56,869 DEBUG [DTDEntityResolver] trying to resolve system-id [http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd]
16:29:56,869 DEBUG [DispatcherThread] failed to retrieve next waiting due job
org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1528)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1462)
at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
at org.jbpm.svc.Services.getService(Services.java:160)
at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
at org.jbpm.job.executor.DispatcherThread.getNextDueDateWithinIdleInterval(DispatcherThread.java:193)
at org.jbpm.job.executor.DispatcherThread.run(DispatcherThread.java:70)
Caused by: org.dom4j.DocumentException: www.hibernate.org Nested exception: www.hibernate.org
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1518)
{noformat}
Looking through the installed JBoss ESB 4.12, I found {{www.hibernate.com...}} in the {{deploy/jbpm.esb/hibernate.cfg.xml}}.
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd">
{code}
Changing {{hibernate.cfg.xml}} to the following (taken from ESB 4.10) seems to fix the problem on both RHEL and Windows.
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
{code}
> Get an HibernateException in JbpmJobExector when starting 4.11 out of the box
> -----------------------------------------------------------------------------
>
> Key: JBESB-3816
> URL: https://issues.jboss.org/browse/JBESB-3816
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Deployment
> Affects Versions: 4.11
> Environment: Windows 7
> Reporter: Olle Sundblad
>
> When I download and install (unzip) the 4.11 release and start it using run.bat without any changes whatsoever I get the following stacktrace over and over again.
> end of start console (it started with no errors/warnings):
> 09:57:16,666 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
> 09:57:16,677 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 28s:270ms
> but immediately after I get the following:
> 09:57:31,928 INFO [Configuration] configuring from resource: hibernate.cfg.xml
> 09:57:31,929 INFO [Configuration] Configuration resource: hibernate.cfg.xml
> 09:57:52,939 INFO [Configuration] configuring from resource: hibernate.cfg.xml
> 09:57:52,940 INFO [Configuration] Configuration resource: hibernate.cfg.xml
> 09:57:52,939 ERROR [LockMonitorThread] exception in JbpmJobExector@138.106.178.133:Monitor
> org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1494)
> at org.hibernate.cfg.Configuration.configure(Configuration.java:1428)
> at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
> at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
> at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
> at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
> at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
> at org.jbpm.svc.Services.getService(Services.java:160)
> at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
> at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
> at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
> at org.jbpm.job.executor.LockMonitorThread.unlockOverdueJobs(LockMonitorThread.java:64)
> at org.jbpm.job.executor.LockMonitorThread.run(LockMonitorThread.java:43)
> Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
> at org.dom4j.io.SAXReader.read(SAXReader.java:484)
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1484)
> ... 15 more
> This repeats over and over again until I stop the server.
> I do not get this exception in 4.10 (so my unqualified guess is the jbpm5 stuff is missing the hibernate.cfg.xml or something)
--
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
11 years, 1 month
[JBoss JIRA] (JBESB-3816) Get an HibernateException in JbpmJobExector when starting 4.11 out of the box
by Ian Walker (JIRA)
[ https://issues.jboss.org/browse/JBESB-3816?page=com.atlassian.jira.plugin... ]
Ian Walker commented on JBESB-3816:
-----------------------------------
I have the same issue but on Windows XP. The following configurations generate the same error as above:
JBoss AS 5.1.0.GA + JBoss ESB 4.11
JBoss AS 5.1.0.GA + JBoss ESB 4.12
JBoss ESB 4.12 Server
Running JBoss ESB 4.12 in JBoss AS 6.1.0.Final does not generate an error.
This seems to be a Windows problem; the exact same configuration runs just fine on a *nix system (OSX).
> Get an HibernateException in JbpmJobExector when starting 4.11 out of the box
> -----------------------------------------------------------------------------
>
> Key: JBESB-3816
> URL: https://issues.jboss.org/browse/JBESB-3816
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Deployment
> Affects Versions: 4.11
> Environment: Windows 7
> Reporter: Olle Sundblad
>
> When I download and install (unzip) the 4.11 release and start it using run.bat without any changes whatsoever I get the following stacktrace over and over again.
> end of start console (it started with no errors/warnings):
> 09:57:16,666 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
> 09:57:16,677 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 28s:270ms
> but immediately after I get the following:
> 09:57:31,928 INFO [Configuration] configuring from resource: hibernate.cfg.xml
> 09:57:31,929 INFO [Configuration] Configuration resource: hibernate.cfg.xml
> 09:57:52,939 INFO [Configuration] configuring from resource: hibernate.cfg.xml
> 09:57:52,940 INFO [Configuration] Configuration resource: hibernate.cfg.xml
> 09:57:52,939 ERROR [LockMonitorThread] exception in JbpmJobExector@138.106.178.133:Monitor
> org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1494)
> at org.hibernate.cfg.Configuration.configure(Configuration.java:1428)
> at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
> at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
> at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
> at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
> at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
> at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
> at org.jbpm.svc.Services.getService(Services.java:160)
> at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
> at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
> at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
> at org.jbpm.job.executor.LockMonitorThread.unlockOverdueJobs(LockMonitorThread.java:64)
> at org.jbpm.job.executor.LockMonitorThread.run(LockMonitorThread.java:43)
> Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
> at org.dom4j.io.SAXReader.read(SAXReader.java:484)
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1484)
> ... 15 more
> This repeats over and over again until I stop the server.
> I do not get this exception in 4.10 (so my unqualified guess is the jbpm5 stuff is missing the hibernate.cfg.xml or something)
--
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
11 years, 1 month
[JBoss JIRA] (JBESB-3898) EBWS on CXF fails to handle WS-Security header with soap:mustUnderstand="1"
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3898?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3898:
------------------------------------------------
Tadayoshi Sato <tasato(a)redhat.com> made a comment on [bug 947862|https://bugzilla.redhat.com/show_bug.cgi?id=947862]
FYI, this patch resolves the issue.
--- webservice_consumer1/war/src/org/jboss/soa/esb/samples/quickstart/webservice_consumer1/HelloWorldWS.java
+++ webservice_consumer1/war/src/org/jboss/soa/esb/samples/quickstart/webservice_consumer1/HelloWorldWS.java
@@ -28,7 +28,7 @@ import javax.jws.WebParam;
@WebService(name = "HelloWorld", targetNamespace = "http://webservice_consumer1/helloworld")
public class HelloWorldWS
{
- @WebMethod
+ @WebMethod(action = "sayHello")
public String sayHello(@WebParam(name = "toWhom")
String toWhom)
{
> EBWS on CXF fails to handle WS-Security header with soap:mustUnderstand="1"
> ---------------------------------------------------------------------------
>
> Key: JBESB-3898
> URL: https://issues.jboss.org/browse/JBESB-3898
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.11
> Environment: SOA-P installed with JBoss WS CXF stack
> Reporter: Tadayoshi Sato
> Assignee: Magesh Bojan
> Fix For: 4.12
>
>
> On JBoss WS CXF, EBWS (ESB-based web service) throws SOAP Faults when handling SOAP requests with the WS-Security UsernameToken header which is declared with {{soap:mustUnderstand="1"}}, even though {{<security moduleName="..."/>}} (I believe this enables WS-Security for EBWS) is set up for the EBWS in {{jboss-esb.xml}}.
> Note that I confirmed JBoss WS CXF itself can handle WS-Security with {{soap:mustUnderstand="1"}} if {{jbossws-cxf.xml}} is properly set up. So, I suspect the problem would be in EBWS.
> I used the following SOAP request:
> {code}
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:say="http://www.jboss.org/sayHi" xmlns:cust="http://www.jboss.org/custom-request" xmlns:sub="http://www.jboss.org/custom-subtype" xmlns:t="http://www.jboss.org/type2">
> <soap:Header>
> <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd">
> <wsse:UsernameToken>
> <wsse:Username>kermit</wsse:Username>
> <wsse:Password>thefrog</wsse:Password>
> </wsse:UsernameToken>
> </wsse:Security>
> </soap:Header>
> <soap:Body>
> ...
> </soap:Body>
> </soap:Envelope>
> {code}
> And got the following SOAP Fault:
> {code}
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> <soap:Header>
> <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"/>
> </soap:Header>
> <soap:Body>
> <soap:Fault>
> <faultcode>soap:MustUnderstand</faultcode>
> <faultstring>MustUnderstand headers: [{http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd}Security] are not understood.</faultstring>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
> {code}
> I also got the following error stacktrace:
> {code}
> 17:04:09,572 WARNING [PhaseInterceptorChain] Interceptor for {http://soa.jboss.org/ESBServiceSample}HelloWorldPubServiceService#{http://soa.jboss.org/ESBServiceSample}HelloWorldPubServiceOp has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: MustUnderstand headers: [{http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd}Security] are not understood.
> at org.apache.cxf.binding.soap.interceptor.MustUnderstandInterceptor$UltimateReceiverMustUnderstandInterceptor.handleMessage(MustUnderstandInterceptor.java:225)
> at org.apache.cxf.binding.soap.interceptor.MustUnderstandInterceptor$UltimateReceiverMustUnderstandInterceptor.handleMessage(MustUnderstandInterceptor.java:199)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.internalProcess(ActiveRequestResponseCacheValve.java:74)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:47)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
> {code}
--
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
11 years, 1 month
[JBoss JIRA] (JBESB-3906) Backport JBESB-3898 to JBESB_4_11_CP2 branch
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3906?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3906:
------------------------------------------------
Tadayoshi Sato <tasato(a)redhat.com> made a comment on [bug 947862|https://bugzilla.redhat.com/show_bug.cgi?id=947862]
FYI, this patch resolves the issue.
--- webservice_consumer1/war/src/org/jboss/soa/esb/samples/quickstart/webservice_consumer1/HelloWorldWS.java
+++ webservice_consumer1/war/src/org/jboss/soa/esb/samples/quickstart/webservice_consumer1/HelloWorldWS.java
@@ -28,7 +28,7 @@ import javax.jws.WebParam;
@WebService(name = "HelloWorld", targetNamespace = "http://webservice_consumer1/helloworld")
public class HelloWorldWS
{
- @WebMethod
+ @WebMethod(action = "sayHello")
public String sayHello(@WebParam(name = "toWhom")
String toWhom)
{
> Backport JBESB-3898 to JBESB_4_11_CP2 branch
> --------------------------------------------
>
> Key: JBESB-3906
> URL: https://issues.jboss.org/browse/JBESB-3906
> Project: JBoss ESB
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.11
> Reporter: Tadayoshi Sato
> Assignee: Tadayoshi Sato
> Fix For: 4.11 CP3
>
>
> Backport JBESB-3898 (EBWS on CXF fails to handle WS-Security header with soap:mustUnderstand="1") to JBESB_4_11_CP2 branch.
--
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
11 years, 1 month
[JBoss JIRA] (JBESB-3898) EBWS on CXF fails to handle WS-Security header with soap:mustUnderstand="1"
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3898?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3898:
------------------------------------------------
Tadayoshi Sato <tasato(a)redhat.com> made a comment on [bug 947862|https://bugzilla.redhat.com/show_bug.cgi?id=947862]
I now understand that SOAPClient [1] has to be changed to conform with CXF upgrade introduced by BZ915386 (more specifically BZ858926 or BZ896338). I will file a different BZ for this issue.
[1] JBESB_4_11_CP2/product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SOAPClient.java
523 PostMethod post = new PostMethod(endpoint);
524
525 post.setRequestHeader("Content-Type", contentType);
526 post.setRequestHeader("Connection", "keep-alive");
527 post.setRequestHeader("SOAPAction", "\"" + soapAction + "\""); /// Customization to add quotes to Soap action
> EBWS on CXF fails to handle WS-Security header with soap:mustUnderstand="1"
> ---------------------------------------------------------------------------
>
> Key: JBESB-3898
> URL: https://issues.jboss.org/browse/JBESB-3898
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.11
> Environment: SOA-P installed with JBoss WS CXF stack
> Reporter: Tadayoshi Sato
> Assignee: Magesh Bojan
> Fix For: 4.12
>
>
> On JBoss WS CXF, EBWS (ESB-based web service) throws SOAP Faults when handling SOAP requests with the WS-Security UsernameToken header which is declared with {{soap:mustUnderstand="1"}}, even though {{<security moduleName="..."/>}} (I believe this enables WS-Security for EBWS) is set up for the EBWS in {{jboss-esb.xml}}.
> Note that I confirmed JBoss WS CXF itself can handle WS-Security with {{soap:mustUnderstand="1"}} if {{jbossws-cxf.xml}} is properly set up. So, I suspect the problem would be in EBWS.
> I used the following SOAP request:
> {code}
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:say="http://www.jboss.org/sayHi" xmlns:cust="http://www.jboss.org/custom-request" xmlns:sub="http://www.jboss.org/custom-subtype" xmlns:t="http://www.jboss.org/type2">
> <soap:Header>
> <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd">
> <wsse:UsernameToken>
> <wsse:Username>kermit</wsse:Username>
> <wsse:Password>thefrog</wsse:Password>
> </wsse:UsernameToken>
> </wsse:Security>
> </soap:Header>
> <soap:Body>
> ...
> </soap:Body>
> </soap:Envelope>
> {code}
> And got the following SOAP Fault:
> {code}
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
> <soap:Header>
> <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"/>
> </soap:Header>
> <soap:Body>
> <soap:Fault>
> <faultcode>soap:MustUnderstand</faultcode>
> <faultstring>MustUnderstand headers: [{http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd}Security] are not understood.</faultstring>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
> {code}
> I also got the following error stacktrace:
> {code}
> 17:04:09,572 WARNING [PhaseInterceptorChain] Interceptor for {http://soa.jboss.org/ESBServiceSample}HelloWorldPubServiceService#{http://soa.jboss.org/ESBServiceSample}HelloWorldPubServiceOp has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: MustUnderstand headers: [{http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd}Security] are not understood.
> at org.apache.cxf.binding.soap.interceptor.MustUnderstandInterceptor$UltimateReceiverMustUnderstandInterceptor.handleMessage(MustUnderstandInterceptor.java:225)
> at org.apache.cxf.binding.soap.interceptor.MustUnderstandInterceptor$UltimateReceiverMustUnderstandInterceptor.handleMessage(MustUnderstandInterceptor.java:199)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.internalProcess(ActiveRequestResponseCacheValve.java:74)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:47)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
> {code}
--
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
11 years, 1 month