esb 4.3 stack trace question...

[fil78]

Hello people!

After I installed esb 4.3GA I got the following stack starting jboss-4.2.2:

13:06:17,123 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.esb:service=JBPMDatabaseInitializer
 State: FAILED
 Reason: org.jboss.deployment.DeploymentException: No Attribute found with name: UseEOL
 I Depend On:
 jboss.jca:service=DataSourceBinding,name=JbpmDS
 Depends On Me:
 jboss.esb:service=JbpmService
 jboss.esb:deployment=jbpm.esb

ObjectName: jboss.esb:service=JbpmService
 State: CONFIGURED
 I Depend On:
 jboss.esb:service=JBPMDatabaseInitializer

ObjectName: jboss.esb:deployment=jbpm.esb
 State: NOTYETINSTALLED
 I Depend On:
 jboss.jca:service=DataSourceBinding,name=JbpmDS
 jboss.esb:service=JBPMDatabaseInitializer
 jboss.esb:deployment=jbossesb.esb

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.esb:service=JBPMDatabaseInitializer
 State: FAILED
 Reason: org.jboss.deployment.DeploymentException: No Attribute found with name: UseEOL
 I Depend On:
 jboss.jca:service=DataSourceBinding,name=JbpmDS
 Depends On Me:
 jboss.esb:service=JbpmService
 jboss.esb:deployment=jbpm.esb

and the following:

13:06:19,435 WARN [MessageAwareListener] Error processing courier, backing off for 8000 milliseconds
13:06:19,466 WARN [MessageAwareListener] Error processing courier, backing off for 8000 milliseconds
13:06:19,466 WARN [MessageAwareListener] Error processing courier, backing off for 8000 milliseconds
13:06:19,466 WARN [MessageAwareListener] Error processing courier, backing off for 8000 milliseconds
13:06:24,495 WARN [MessageAwareListener] Error processing courier, backing off for 1000 milliseconds
13:06:28,494 INFO [JmsConnectionPool] Received NamingException, refreshing context.
13:06:32,446 INFO [JmsConnectionPool] Received NamingException, refreshing context.
13:06:32,477 INFO [JmsConnectionPool] Received NamingException, refreshing context.
13:06:32,477 INFO [JmsConnectionPool] Received NamingException, refreshing context.

Does anybody could explain the reason?

Thanx a lot...

[beve]

Hi,

can you post the steps you took so that I can try and reproduce this issue?

My understanding is that you have downloaded jbossesb-4.3.GA and installed it into jboss-4.2.2.GA. Is that correct?

Thanks,

Daniel

[fil78]

Yes, that is correct - I had esb 4.2.1 installed before and then I installed 4.3. Immediately after it I got this error. Besides I had some jBPM processes and esb projects on my server. I deleted some - it would not help.

Thanx.

[beve]

Hi,

it looks like your jbossesb-rosetta.jar has not been updated correctly after the upgrade.
The field 'UseEOL' is a new field in the DatabaseInitializer class and did not exist in 4.2.1_GA.

The DatabaseInitializer class is located in jbossesb-rosetta.jar which is in the lib directory in jbossesb.sar.
If you run 'java -jar jbossesb-rosetta.jar' which version does it display?

Regards,

Daniel

[fil78]

Yes - there is the root... - it is 4.2.1... - It means that I could not start installation of new version untill I kill the previous? How could I do it? And does jBPM db for 4.3 version has any differences from 4.2.1 version?

Thanx a lot.

[kconner]

You should start with as clean an installation as possible as there are a number of differences. The jBPM integration is certainly one area that has changed as the 4.2.1 integrationhad some serious issues.

If you cannot start from a clean AS installation then please make sure that you remove the following from the deploy directory.

all .esb artifacts
jbossesb.sar
soapui-client.sar
jbossesb-config-editor.war
contract.war
management-ds.xml

[mvecera]

Hello,

I've experienced similar problem when I had misconfigured JbpmDS. Try checking it as well.

[kconner]

Martin, the issue is that it was picking up the old initlalizer MBean from the 4.2.1 distribution.

The new MBean has a UseEOL attribute that allows us to use the hibernate generated jBPM files as created.