[JBoss JIRA] Created: (JBESB-2928) Unnecessary Warnings in Admin Console
by Fernando Ribeiro (JIRA)
Unnecessary Warnings in Admin Console
-------------------------------------
Key: JBESB-2928
URL: https://jira.jboss.org/jira/browse/JBESB-2928
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.6
Reporter: Fernando Ribeiro
01:11:55,820 WARN [Initialization] <action expression="#{redirect.captureCurrentView}" /> has been deprecated, use <action execute="#{redirect.captureCurrentView}" /> instead
01:11:55,825 WARN [Initialization] <action expression="#{redirect.returnToCapturedView}" /> has been deprecated, use <action execute="#{redirect.returnToCapturedView}" /> instead
01:11:56,463 WARN [Component] Component class should be serializable: navigationAction
01:11:56,496 WARN [Component] Component class should be serializable: operationAction
01:11:57,151 WARN [Component] Component class should be serializable: resourceConfigurationUIBean
01:11:57,199 WARN [Component] Component class should be serializable: resourceTypeContentAction
01:11:57,229 WARN [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required.
01:12:05,218 WARN [SystemInfoFactory] System info API not accessible on this platform (native shared library not found in java.library.path).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2922) SchemaValidationActionUnitTest test failure serialising DOM
by Kevin Conner (JIRA)
SchemaValidationActionUnitTest test failure serialising DOM
-----------------------------------------------------------
Key: JBESB-2922
URL: https://jira.jboss.org/jira/browse/JBESB-2922
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.6
Reporter: Kevin Conner
Assignee: Tom Fennelly
Fix For: 4.7
The following error is being seen on the CI machines, executing on JDK 1.6
[java] [junit] java.lang.RuntimeException: Unexpected error. Unable to serialize DOM.
[java] [junit] at org.jboss.soa.esb.actions.validation.ValidationException.getDomResult(ValidationException.java:59)
[java] [junit] at org.jboss.soa.esb.actions.validation.SchemaValidationActionUnitTest.processInvalidXml(SchemaValidationActionUnitTest.java:65)
[java] [junit] Caused by: org.xml.sax.SAXParseException: Premature end of file.
[java] [junit] at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
[java] [junit] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
[java] [junit] at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
[java] [junit] at org.jboss.soa.esb.dom.YADOMUtil.parseStream(YADOMUtil.java:148)
[java] [junit] at org.jboss.soa.esb.dom.YADOMUtil.parseStream(YADOMUtil.java:114)
[java] [junit] at org.jboss.soa.esb.dom.YADOMUtil.parse(YADOMUtil.java:95)
[java] [junit] at org.jboss.soa.esb.actions.validation.ValidationException.getDomResult(ValidationException.java:51)
Tom, are we trying to serialise parser specific classes here? If so this will fail in a mixed environment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2870) war/esb archive deployment dependencies/ordering not guaranteed
by David Ward (JIRA)
war/esb archive deployment dependencies/ordering not guaranteed
---------------------------------------------------------------
Key: JBESB-2870
URL: https://jira.jboss.org/jira/browse/JBESB-2870
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.6
Reporter: David Ward
Fix For: 4.7
There should be a way to specify that an esb archive is dependent on a war archive to be deployed first before it is deployed.
An example of this is a SOAPProxy action which points to a JBossWS webservice deployed in the same container.
Right now, one can specify a deployment requirement of a war from an esb's deployment.xml file, but there are 2 problems with it:
1. You need to know the entire war deployment mbean object name, which unfortunately contains a generated id
2. The esb deployment will simply error instead of waiting for the dependent war to deploy.
It is probable that we need to create our own barrier for this to work properly.
We also need to test with wars contained inside esb archives, as well as exploded and zipped wars.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2926) Ant deploy script (in product/build/jbossesb/build) failing
by Tom Fennelly (JIRA)
Ant deploy script (in product/build/jbossesb/build) failing
-----------------------------------------------------------
Key: JBESB-2926
URL: https://jira.jboss.org/jira/browse/JBESB-2926
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Tom Fennelly
Fix For: 4.7
Fails with the following error...
internal.deploy.jbossas5:
[echo] Deploy to JBossAS5
[mkdir] Created dir: H:\jboss-5.1.0.GA\server\default\deployers\esb.deployer
[copy] Copying 51 files to H:\jboss-5.1.0.GA\server\default\deployers\esb.deployer\lib
[copy] Copying 2 files to H:\jboss-5.1.0.GA\server\default\deployers\esb.deployer\META-INF
[copy] Copying 5 files to H:\jboss-5.1.0.GA\server\default\deployers\esb.deployer
BUILD FAILED
H:\jboss\esb\trunk\product\build\jbossesb\install\build.xml:292: H:\jboss\esb\trunk\product\build\jbossesb\build\lib not found.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2787) jbpm.esb causes AS 5 server to sometimes hang upon shutdown.
by Daniel Bevenius (JIRA)
jbpm.esb causes AS 5 server to sometimes hang upon shutdown.
-------------------------------------------------------------
Key: JBESB-2787
URL: https://jira.jboss.org/jira/browse/JBESB-2787
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.7
Reporter: Daniel Bevenius
The application server does not close down, well it hangs for a long while before finishing.
Console log (a few mins after the thread dump)
=============================================
16:54:33,395 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted atomic action 7f000001:a6d0:4a82d3c0:3cb
16:54:33,395 ERROR [STDERR] Exception in thread "JbpmJobExector:127.0.0.1:1"
16:54:33,395 ERROR [STDERR] java.lang.StackOverflowError
16:54:33,400 ERROR [STDERR] at java.lang.Class.isPrimitive(Native Method)
16:54:33,400 ERROR [STDERR] at java.lang.Class.getEnclosingMethodInfo(Class.java:923)
16:54:33,400 ERROR [STDERR] at java.lang.Class.getEnclosingClass(Class.java:1077)
16:54:33,400 ERROR [STDERR] at java.lang.Class.getSimpleBinaryName(Class.java:1216)
16:54:33,401 ERROR [STDERR] at java.lang.Class.getSimpleName(Class.java:1108)
16:54:33,401 ERROR [STDERR] at org.jboss.classloader.spi.base.BaseClassLoader.toString(BaseClassLoader.java:926)
16:54:33,401 ERROR [STDERR] at java.lang.String.valueOf(String.java:2615)
16:54:33,401 ERROR [STDERR] at java.lang.StringBuilder.append(StringBuilder.java:116)
16:54:33,401 ERROR [STDERR] at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:138)
16:54:33,401 ERROR [STDERR] at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620)
16:54:33,401 ERROR [STDERR] at org.jboss.system.JBossRMIClassLoader.loadClass(JBossRMIClassLoader.java:91)
16:54:33,401 ERROR [STDERR] at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)
16:54:33,401 ERROR [STDERR] at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
16:54:33,402 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
16:54:33,402 ERROR [STDERR] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
16:54:33,402 ERROR [STDERR] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
16:54:33,402 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
16:54:33,402 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
16:54:33,402 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351)
16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:162)
16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172)
...
16:54:33,996 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=JbpmDS' from JNDI name 'java:JbpmDS'
16:54:34,044 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
16:54:34,044 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
16:54:34,045 INFO [SimpleThreadPool] There are still 35 worker threads active. See javadoc runInThread(Runnable) for a possible explanation
16:54:34,045 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
16:54:34,528 INFO [TransactionManagerService] Stopping transaction recovery manager
16:54:34,530 INFO [TransactionManagerService] Destroying TransactionManagerService
16:54:34,685 INFO [HypersonicDatabase] Database standalone closed clean
16:54:38,218 INFO [DefaultEndpointRegistry] remove: jboss.ws:context=Quickstart_webservice_consumer2,endpoint=OrderProcessorWS
16:54:38,402 INFO [HypersonicDatabase] Database standalone closed clean
16:54:38,661 INFO [H2Database] Database standalone closed clean
16:54:48,022 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
Complete log will be attached with a thread dump.
I found this jira: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3481
The version of hibernate that is shipped with AS 5.1.0.GA is 3.3.1. Perhaps an upgrade to 3.3.2 will take care of the issue with the hang, though I still think
that we will in that case get an exception. Should the jbpm.esb/jbpm-service.xml's JbpmService depend on the TransactionManager?:
<mbean code="org.jboss.soa.esb.services.jbpm.configuration.JbpmService"
name="jboss.esb:service=JbpmService">
<depends>jboss.esb:service=JBPMDatabaseInitializer</depends>
<depends>jboss:service=TransactionManager</depends>
</mbean>
Lets say the TransactionManager sometimes gets deployed before the jbpm.esb, then this would probably trigger this issue. Sort of difficult to test this as this does not happen every time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBESB-2925) 'jboss.web.deployment:war=/juddi is already installed' error in JBoss AS 5.1.0 (all config)
by Jeff Yu (JIRA)
'jboss.web.deployment:war=/juddi is already installed' error in JBoss AS 5.1.0 (all config)
-------------------------------------------------------------------------------------------
Key: JBESB-2925
URL: https://jira.jboss.org/jira/browse/JBESB-2925
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.6
Reporter: Jeff Yu
Fix For: 4.7
detailed log as following:
steps to reproduce this error.
1. install the JBoss ESB 4.6 into JBoss AS 5.1.0 all config (not default)
2. start the AS server.
==============
11:25:25,052 ERROR [WebModule] Could not create JSR-77 WebModule: juddi.war
javax.management.InstanceAlreadyExistsException: jboss.management.local:j2eeType=WebModule,J2EEServer=Local,J2EEApplication=null,name=juddi.war already registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:756)
at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:233)
at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months