• RELEVANCY SCORE 5.57

    DB:5.57:Samples\Quickstarts\Exceptions_Faults zm






    who can run the samples\quickstarts\exceptions_faults of jboss esb server 4.7

    SendEsbMessage and SendEsbMessageSync i can't run both

    DB:5.57:Samples\Quickstarts\Exceptions_Faults zm


    who can run the samples\quickstarts\exceptions_faults of jboss esb server 4.7

    SendEsbMessage and SendEsbMessageSync i can't run both

  • RELEVANCY SCORE 4.36

    DB:4.36:Urgent :: Problem With Helloworld :: Build Failed On Deploy 1a






    hiI am new to jbossesb.I m following all step mentioned in PDF for deploying quickstarts's helloworld sample but i get following error.

    Buildfile: C:\workspace-ESB\jbossESB\samples\quickstarts\helloworld\build.xml
    prepare:
    compile:
    jars:
    [jar] Building jar: C:\workspace-ESB\jbossESB\samples\quickstarts\helloworld\build\Quickstart_helloworld.jar
    deployToSAR:
    [echo] Deploys the project to the JBoss Application Server ESB SAR
    [copy] Copying 1 file to C:\jboss-4.0.5.GA\server\default\deploy\jbossesb.sar
    [copy] Copying 1 file to C:\jboss-4.0.5.GA\server\default\conf
    [touch] Creating C:\jboss-4.0.5.GA\server\default\deploy\jbossesb.sar\META-INF\jboss-service.xml

    BUILD FAILED
    C:\workspace-ESB\jbossESB\samples\quickstarts\helloworld\build.xml:74: Could not create C:\jboss-4.0.5.GA\server\default\deploy\jbossesb.sar\META-INF\jboss-service.xml

  • RELEVANCY SCORE 4.35

    DB:4.35:Cluster Of Jboss Esb? aj






    will JBoss ESB add cluster feature?

    DB:4.35:Cluster Of Jboss Esb? aj


    Hallo Koybe,

    JBoss ESB support Clustering. See ESB Programmers Guide Chapter 7 : Advanced Topic

    Regards

    Younes

  • RELEVANCY SCORE 4.31

    DB:4.31:Trouble Getting Quickstarts To Run zm



    When I am trying to run the quickstarts in version 4.3, I am getting the following error. Are there any recommendations for resolving this error? I am attempting to start the quickstarts in a Windows XP environment, and am using the standalone server included in the JBoss ESB distribution. [qsjava] javax.naming.CommunicationException: Could not obtain connection toany of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]

    DB:4.31:Trouble Getting Quickstarts To Run zm


    Okay, that makes sense. Presumably the bat script could not find the java executable in that case.

  • RELEVANCY SCORE 4.29

    DB:4.29:Esb - First Steps m1


    Hi Integration Guru!

    Recently I was intended to get experience with integration software and ESB. As I found currently we have the next popular ESB solutions: Jboss ESB, TIBCO ActiveMatrix SB and Websphere ESB. For open source we have eMule, ServiceMix and Open ESB.
    If you started work with ESB today what would you prefer? And what is easer to get start and for Eclipse of course :)

    Any thoughts are highly appreciated..

    DB:4.29:Esb - First Steps m1

    Hi Chis,

    We have multiple server socket's connections and to process data we use linked queue. This queue is shared by working threads that call apropriate data hadlers. I would like to transform shared queue to JMS message queue and use ESB to call appropriate services to process incoming messages.
    I tend to open source solution but not sure where to start :)

    Thank you for your time.

  • RELEVANCY SCORE 4.22

    DB:4.22:Jboss Esb Beginner dp



    Hi

    Is there a forum for beginner?

    Thanks.

  • RELEVANCY SCORE 4.05

    DB:4.05:Memory Leak In Content Based Router f1



    Hey,I may have found a memory leak in the Content Based Router in both JBoss ESB 4.2.1 and 4.3.I noticed the problem at my Job with a production JBoss ESB 4.2.1 CP2 because it regularly crashed because the memory run out. After doing some memory analysis I found that the problem was with the content based router.To reliably reproduce the problem I created a sample project using the simple_cbr sample. I made that project available for download. The link is at the end of this post. I also included an export from a memory analysis of a memory dump. In that dump you can clearly see that the org.drools.base.FireAllRulesRuleBaseUpdateListener objects are piling up. Because the problem is within Drools I am not sure if the problem is really in the ESB.The test environment is:Java 1.5 or 6.0JBoss 4.2.2 GAJBoss ESB 4.2.1 or 4.3Memory settings: -Xms256m -Xmx256m -XX:MaxPermSize=128mThe memory leak sample project can be downloaded here: http://www.smies.com/downloads/jbossesb/memory_leak_cbr.zipSimply unpack the project within the sample/quickstarts directoy to make it work.

    DB:4.05:Memory Leak In Content Based Router f1


    The issue you have identified has been fixed in the drools code base but there is a workaround for our environment :)The ReteooRuleBase is accumulating the event handlers (which contain session references) without releasing them. These handlers are used to notify the sessions of any updates to the rule base (which we never do) so the simple workaround is to disable their use.The easiest way to achieve this is to start the server with the following on the command line
    -Ddrools.ruleBaseUpdateHandler

  • RELEVANCY SCORE 4.04

    DB:4.04:About Data Store 7d



    A few dates ago, I installed jboss esb server, and meanwhile I changed database from Hypersonic to MySQL.

    At that time, I just think that I must persist my data into database rather than kind of memory.

    It runs ok now, I was very happy that I can deploy jPDL to MySQL, and some other data can also be stored in MySQL.

    But when I tried to run [samples\quickstarts\jms_transacted], I found that you can also define your own datasource to persist messages.

    Then why we need to transform database from Hypersonic to MySQL except jbpm.esb?

    Can anyone who tell me the function of following configurations under [jbossesb-server-4.7\server\default\deploy]

    \jbossesb.esb

    \jbossesb.sar

    \jbossesb-registry.sar

    \jboss-messaging.sar

    \hsqldb-ds.xml

    I'm not clear that esb server help us to automatically persist what kind of data?

    And then, as a developer we also need to persist what kind of data?

    Thanks,

    Simon

    DB:4.04:About Data Store 7d


    1.4. Database Configuration

    The ESB uses a database for persisting Registry services, and the Message-Store.

    -

    what kind of situation ESB would persist messages into database automatically?

    eh....

    Actually, when ESB server would insert messages into table of message?

  • RELEVANCY SCORE 3.99

    DB:3.99:Quickstarts Probem: Jbossas 4.0.5 Ga Esb Mr2 pm



    Hi!I just installed JBossAS 4.0.5GA with the jems installer and with the EJB3 option selected. Dowloaded the JBossESB 4.2MR2, installed jbossesb.sar.The server started without error, so I tried to deploy the helloword quickstart.During the deploy I got the following error on the server console:13:10:27,871 ERROR [MainDeployer] Could not create deployment: file:/home/zvadasz/Programs/JBoss/jboss-4.0.5.GA/server/default/tmp/deploy/tmp13118Quickstart_helloworld.esb-contents/jbm-queue-service.xmlorg.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.jms.server.destination.QueueService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.server.destination.QueueService)[...]Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.server.destination.QueueService[...]I googled but found nothing relevant :-(I did the whole procedure 3 times to be sure: I accurately follow the instructions in the GettingStartedGuide and in the helloword sample's documentation.What't wrong? What other information do you need to be abe to help?

    DB:3.99:Quickstarts Probem: Jbossas 4.0.5 Ga Esb Mr2 pm


    No problem.The code in trunk has been changed to identify the message implementation being used in the server and automatically deploy the correct configuration files.Please let us know if you experience any other problems.

  • RELEVANCY SCORE 3.87

    DB:3.87:What Is Correct Location For Jbossesb-Properties.Xml? pp



    Running JBoss SOA/ESB 5.0.2.

    Documentation always makes reference to jbossesb-properties.xml being in ${JBOSS_HOME}/server/default/deploy/jbossesb.sar.

    In the out of box installation, this file does not exist in this directory.

    However, I do see this file in the quickstarts and it gets packaged with the application when you run an "ant deploy".

    So question is, should the jbossesb-properties.xml be copied to ${JBOSS_HOME}/server/default/deploy/jbossesb.sar

    ( as its referenced in the documentation ) or should it be included in the application?

    Thanks.

    Jon

    DB:3.87:What Is Correct Location For Jbossesb-Properties.Xml? pp


    Hmmyes,

    but what is the one in data generated from !?

    When I do

    $ ls -l `find jboss-esb -name "jbossesb-properties.xml" | grep -v samples`

    -rw-r--r-- 1 teicher staff 7285 30 Jan xx:xx jboss-esb/server/default/data/jbossesb-properties.xml

    -rw-r--r-- 1 teicher staff 11478 8 Nov xx:xx jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml

    $ rm jboss-esb/server/default/data/jbossesb-properties.xml

    $ ./jboss-esb/bin/run.sh

    --- let it startup --- stop with CTRL-C ---

    $ ls -l `find jboss-esb -name "jbossesb-properties.xml" | grep -v samples`

    -rw-r--r-- 1 teicher staff 7285 30 Jan xx:xx jboss-esb/server/default/data/jbossesb-properties.xml

    -rw-r--r-- 1 teicher staff 11478 8 Nov xx:xx jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml

    My problem is: the one in data is incomplete / has the old timeout setting:

    overmax:jboss-soa-p-standalone-5 teicher$ grep ftp.timeout `find jboss-esb -name "jbossesb-properties.xml" | grep -v samples`

    jboss-esb/server/default/data/jbossesb-properties.xml: property name="org.jboss.soa.esb.ftp.timeout" value="0" /

    jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml: !-- Coarse-grained ftp timeout property in milliseconds (0 = infinite). The fine-grained properties below will default to this value if not set. See FtpUtils javadoc for more info. --

    jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml: property name="org.jboss.soa.esb.ftp.timeout" value="0"/

    jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml: !-- Fine-grained ftp timeout property which sets the default timeout to use when opening a socket. Not to be confused with timeout.so which operates on the currently opened socket. --

    jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml: !-- property name="org.jboss.soa.esb.ftp.timeout.default" value="0"/ --

    jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml: !-- Fine-grained ftp timeout property which sets the timeout to use when reading from the data connection. --

    jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml: !-- property name="org.jboss.soa.esb.ftp.timeout.data" value="0"/ --

    jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml: !-- Fine-grained ftp timeout property which sets the timeout of a currently open connection.--

    jboss-esb/server/default/deployers/esb.deployer/jbossesb-properties.xml: !-- property name="org.jboss.soa.esb.ftp.timeout.so" value="0"/ --

    Actually the one in data looks really old, before JBESB-3177, but I cannot find it or it's values in my whole workspace or anywhere else on disk.

    So, repeat: from what is the jbossesb-properties.xml in data generated !?

    Thanks, Cheers, Tom.

  • RELEVANCY SCORE 3.84

    DB:3.84:Windows Installation For Jboss Esb aj



    Where can ifind the windows installation for JBoss. ESB.

  • RELEVANCY SCORE 3.73

    DB:3.73:Eclipse, Esb 4.11 And Remote Serviceinvoker Problems 1p



    Hi all

    I have some problems with Eclipse 3.6, ESB 4.11, JBoss AS 6.1.0 on Linux OpenSuse 11.4 x64 with java jdk 1.6.0 x64. When I try to build and deploy quickstarts projects in jbossesb-4.11/samples/, with "ant deploy", all is ok and samples run. But when I try to start with an Eclipse project, for example one based on "helloword", with ServiceInvoker class I get the following unbearable exception:

    Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException
    etc.
    Ok, no problem. I have not experience with JBoss ESB and with so much patience, I start looking for a solution in web. Soon I realized that the problem seems common. I have done everything that is written here (the problem seems the same): https://community.jboss.org/thread/144658, but nothing: no results. Then I have read carefully "Configuration for a Remote Service Invoker" in "ESB Programmers Guide", but still no results.

    My code is very simple:

    System.setProperty("javax.xml.registry.ConnectionFactoryClass","org.apache.ws.scout.registry.ConnectionFactoryImpl"); Message message = MessageFactory.getInstance().getMessage(); message.getBody().add("test test test"); ServiceInvoker serviceInvoker = new ServiceInvoker("FirstServiceESB", "SimpleListener"); serviceInvoker.deliverAsync(esbMessage);

    The exception borns when I try to call new ServiceInvoker. I'm sure that the problems are in classpath, but the jar listed in https://community.jboss.org/thread/144658 and in "Configuration for a Remote Service Invoker" are all in my classpath; also I have checked the base-build.xml ant script and in my Eclipse project all seems correct. Also in the Eclipse project there are "JBoss ESB Runtime" and "JBoss 6 Runtime" library references; uddi.xml, jbossesb-properties.xml, etc. are all in my classpath or in my META-INF folder. Finally, after dozens of attempts, not knowing what to do and with no other resources, I tried to run my code with jdk x86 (jdk 1.6.22), but nothing, no results, of course.

    Is there anyone that can help me?

    Regards

    Daniele

    DB:3.73:Eclipse, Esb 4.11 And Remote Serviceinvoker Problems 1p


    Hi Tom

    Thanks for your reply; since nobody had answered to my help request, I have worked around the problem with an ant compile and deploy project. Then, after that, I have the suspect that my problem is not an error in classpath or libraries, but it is perhaps in my Eclipse plugin for JBoss AS configuration (I am new with the JBoss technology...). In fact a simple dynamic web project does not work, even if all the files are deployed in the temp deploy directory of my Jboss AS 6.1. In my Eclipse 3.6, the JBoss AS plugin is for JBoss AS 6.0, but not for JBoss AS 6.1 and the Problems windows of my Eclipse report this as a problem.

    Daniele

  • RELEVANCY SCORE 3.72

    DB:3.72:Can't Install Rest Quickstarts In Jboss-Fuse-6.1.0-2 aa



    Hi,

    I follow instructions in the quckstarts directory jboss-fuse-6.1.0-2.redhat-379/quickstarts/rest

    after running command:

    features:install quickstart-rest

    DB:3.72:Can't Install Rest Quickstarts In Jboss-Fuse-6.1.0-2 aa


    Hi I have a similar problem with the examples in quickstart, specifically for rest and secure-rest

    mvn step runs successfully, now when I try to execute the commands from fuse console for the res example, it doesn't give me any id and in the logs I get this error :

    015-03-20 10:59:55,968 | ERROR | l Console Thread | BlueprintContainerImpl | ?? | 9 - org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Unable to

    start blueprint container for bundle org.jboss.quickstarts.fuse.rest

    org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to initialize bean customerService

    at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:714)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:824)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:787)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_75]

    at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:183)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:676)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:374)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:261)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:270)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:233)[9:org.apache.aries.blueprint.core:1.0.1.redhat-610379]

    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[11:org.apache.aries.util:1.0.1.redhat-610379]

    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[11:org.apache.aries.util:1.0.1.redhat-610379]

    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[11:org.apache.aries.util:1.0.1.redhat-610379]

    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[11:org.apache.aries.util:1.0.1.redhat-610379]

    at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[11:org.apache.aries.util:1.0.1.redhat-610379]

    at org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1103)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:696)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:484)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4650)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.felix.framework.Felix$4.run(Felix.java:2123)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.felix.framework.Felix.runInContext(Felix.java:2147)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.felix.framework.Felix.startBundle(Felix.java:2121)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]

    at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]

    at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:404)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]

    at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:400)[22:org.apache.karaf.features.core:2.3.0.redhat-610379]

    at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)[26:org.apache.karaf.features.command:2.3.0.redhat-610379]

    at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:41)[26:org.apache.karaf.features.command:2.3.0.redhat-610379]

    at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379]

    at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379]

    at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[15:org.apache.felix.gogo.runtime:0.11.0.redhat-610379]

    at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[15:org.apache.felix.gogo.runtime:0.11.0.redhat-610379]

    at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[15:org.apache.felix.gogo.runtime:0.11.0.redhat-610379]

    at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[15:org.apache.felix.gogo.runtime:0.11.0.redhat-610379]

    at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[15:org.apache.felix.gogo.runtime:0.11.0.redhat-610379]

    at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[15:org.apache.felix.gogo.runtime:0.11.0.redhat-610379]

    at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)[15:org.apache.felix.gogo.runtime:0.11.0.redhat-610379]

    at org.apache.karaf.shell.console.jline.Console.run(Console.java:189)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379]

    at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379]

    aused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.cxf.jaxrs.provider.ProviderFactory

    at org.apache.cxf.jaxrs.AbstractJAXRSFactoryBean.setupFactory(AbstractJAXRSFactoryBean.java:327)

    at org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean.java:171)

    at org.apache.cxf.jaxrs.JAXRSServerFactoryBean.init(JAXRSServerFactoryBean.java:135)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_75]

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_75]

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_75]

    at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_75]

    at org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)

    at org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)

    at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:712)

    ... 42 more

    I read in a post that this was fixed for 6.2 release but again wasn't this already resolve here [ENTESB-933] Rest and Secure-rest examples fail to install with javax.ws.rs.NotFoundException - JBoss Issue Tracker

    Thanks

  • RELEVANCY SCORE 3.71

    DB:3.71:Helloworld_Topic_Notifier Vs Jms_Topic xc



    I am trying to design a publish-subscriber example running on JBoss ESB, so I am going through the quickstarts. What is the difference between these two quick starts, at least in terms of how the subscribers/listeners are working?

    What I want to do is have a webservice send a message to the ESB, which publishes it to a topic.

    Then I want to have an example subscriber (other people will be writing their own subscribers, this is just an example to point to and demonstrate the capabilities) which will get notified that there is a message on the topic, get the message, and then it will do something with that message.

    I'm not sure which quickstarts pertain to my intended design, but I think it's a mix of both.

    I think I need the HTTP Gateway quickstart to actually send a message via a webservice to the ESB. Then can it stick it directly on a JMS Topic? Would that be esb aware or unaware?

    Then how do I subscribe to the topic? I need it to be durable, but the topic is (I think) ESB Aware, so would that be the jms_topic quickstart and follow how those subscribers work?

    DB:3.71:Helloworld_Topic_Notifier Vs Jms_Topic xc


    The big overview is: I need to be able to publish a message to a topic, which probably 200 subscribers will be listening to, and they will do something with the message once they get it. They need to be durable subscribers, because one of more of them could go offline for a period of time, and need to process the messages when they get back up. I'm writing just one of those subscribers right now, to showcase how it works. That subscriber is going to call a different webservice which will process the message somehow. I need to know how to handle a scenario where the webservice I'm trying to call is down - that seems to be part 2 of the puzzle.

    And part one of the puzzle is where the subscribers live and how they are configured. So I guess I thought I needed the subscriber to be deployed on the ESB. I'm not sure how it would work otherwise, how it would be deployed on a different server and then still be connected to the ESB (trying to avoid having to mess with mutual ssl, firewalls, ports, etc). I figured having the subscriber (or all 200 of them, all written by different organizations) installed on the ESB would be the best option.

  • RELEVANCY SCORE 3.68

    DB:3.68:How Can I Deploy Jbossesb Administatro Console? zs



    my env:JBoss 4.2.1.GAJBoss ESB 4.2GAJDK 1.5.12Ant 1.6.5I run Ant command in a command terminal,using the following configuration: database type:hsqldb JSF provider:jbossfacesBuild Successful!there generate a file:jboss-esb-console.ear, not jboss-esb-console.war. I copy the file to my application server's deploy directory, but there is an error.---Incompleterly deployed packages ---org.jboss.deployment.DeploymentInfo@a164df1a {Url=file:/C:/jboss-4.2.1.GA/Server/default/deploy/jboss-esb-console.ear } deployer:org.jboss-deployment.EARDeployer@f0cb3c status:null state:FAILED watch:file:/C:/jboss-4.2.1.GA/Server/default/deploy/jboss-esb-console.ear altDD:null lastDeployed:11931149548475 lastModified: 1193114954859 mbeans:I can't enter my Jboss ESB Administrator Console. How can deal with it?

    DB:3.68:How Can I Deploy Jbossesb Administatro Console? zs


    Another thing that should be noted here is that this console is only for transformation management and setup.The main ESB Admin console is available at:http://localhost:8080/jbossesb/I believe in 4.2.0GA it was installed by default. If not, you can review theproduct\tools\console directory and check out the various Readme files.In 4.2.1GA it is/will be installed by default.

  • RELEVANCY SCORE 3.68

    DB:3.68:Jboss Esb Console Deployment From Sources pz



    HelloI have downloaded JBossESB 4.0 RC1 (sources), and after some troubles tested ok quickstarts and trailblazer (I will try to post some suggestions to docs if I have the time to do it)I am using JBoss4.0.5.GA+EJB3 (from installer) + Postgres8.1 + jUDDI manually added (from zip of binary distribution of JBoss4.0.5.GA, did not found how to put it with installer)According to new docs (MessageTransformation.pdf) , there is a new console in /jboss-esb-console, but I am unable to install it.The doc talks about tools folder and tools/console-IMPORT.sqlIn the sources distribution, I only see/product/console, where there is a import.sqlRunning "ant deploy" in /product/console, it generates and deploy a 21Mb jboss-esb-console.war, with errores on JBossAS log11:29:06,552 INFO [STDOUT] ERROR 12-12 11:29:06,547 (AbstractController.java:incrementState:350) -Error installing to Create: name=ServiceEndpointManager state=Configuredjavax.management.InstanceAlreadyExistsException: jboss.ws:service=ServiceEndpointManager already registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:761)...*** DEPLOYMENTS IN ERROR: Name - ErrorSubscriptionManager - javax.management.InstanceAlreadyExistsException: jboss.ws:service=SubscriptionManager,module=eventing already registered.ServiceEndpointManager - javax.management.InstanceAlreadyExistsException: jboss.ws:service=ServiceEndpointManager already registered....Running "ant -f postgres-distro-build.xml" in /product/console/distro, it generates a 41Mb war, and copying it to deploy, there are no errors in JBossAS log, but in http://../jboss-esb-console it appears just a list of filesSuggestions wellcome, and thanks in advance

    DB:3.68:Jboss Esb Console Deployment From Sources pz


    That's great Daniel, thanks.Any suggestions/comments on it?T.

  • RELEVANCY SCORE 3.64

    DB:3.64:Helloworld Exceptions mm



    Hello,I'm trying to get the HellowWorld quickstart running on AS 4.2.0.GA and ESB 4.2 MR2.I first tried step-by-step from the Getting Started Guide. The ant deploy-jms-dests reported no errors, but when I ran just 'ant' to start the ESB I got this:

    C:\Documents and Settings\gzoller\My Documents\libs\JBoss ESB 4.2\samples\quickstarts\helloworldant
    Buildfile: build.xml

    qslib-dependencies:

    non-qslib-dependencies:

    dependencies:

    compile:

    config:

    run:
    [echo] Launching Quickstart in standalone mode...
    [java] +----------------------------------------------------------+
    [java] | |
    [java] | Starting JBossESB... |
    [java] | |
    [java] +----------------------------------------------------------+
    [java] Reading config from C:\Documents and Settings\gzoller\My Documents\libs\JBoss ESB 4.2\samples\quickstarts\helloworld\jboss-esb.xml
    [java] 10:31:42,332 ERROR [main][ConfigurationController] The current versions of the jbossesb-listener.xml and/or jbossesb-gateway.xml are kept
    in place until the error is resolved: Failed to serialize ESB Configuration Document instance.
    [java] org.jboss.soa.esb.ConfigurationException: Failed to serialize ESB Configuration Document instance.
    [java] at org.jboss.soa.esb.dom.YADOMUtil.serialize(YADOMUtil.java:214)
    [java] Exception in thread "main" org.jboss.soa.esb.ConfigurationException: Unable to generate gateway and listener configurations
    [java] at org.jboss.soa.esb.dom.YADOMUtil.serialize(YADOMUtil.java:190)
    [java] at org.jboss.soa.esb.listeners.StandAloneBootStrapper.initiateController(StandAloneBootStrapper.java:205)
    [java] at org.jboss.soa.esb.dom.YADOMUtil.serialize(YADOMUtil.java:176)
    [java] at org.jboss.soa.esb.listeners.config.Generator.generate(Generator.java:162)
    [java] at org.jboss.soa.esb.listeners.config.ConfigurationController.processConfiguration(ConfigurationController.java:306)
    [java] at org.jboss.soa.esb.listeners.config.ConfigurationController.init(ConfigurationController.java:122)
    [java] at org.jboss.soa.esb.listeners.StandAloneBootStrapper.initiateController(StandAloneBootStrapper.java:197)
    [java] at org.jboss.soa.esb.listeners.StandAloneBootStrapper.init(StandAloneBootStrapper.java:132)
    [java] at org.jboss.soa.esb.listeners.StandAloneBootStrapper.init(StandAloneBootStrapper.java:108)
    [java] at org.jboss.soa.esb.listeners.StandAloneBootStrapper.main(StandAloneBootStrapper.java:77)
    [java] Caused by: javax.xml.transform.TransformerException: java.io.FileNotFoundException: C:\Documents%20and%20Settings\gzoller\My%20Documents\l
    ibs\JBoss%20ESB%204.2\samples\quickstarts\helloworld\jbossesb-listener.xml (The system cannot find the path specified)
    [java] at org.apache.xalan.transformer.TransformerIdentityImpl.createResultContentHandler(TransformerIdentityImpl.java:296)
    [java] at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:329)
    [java] at org.jboss.soa.esb.dom.YADOMUtil.serialize(YADOMUtil.java:212)
    [java] ... 9 more
    [java] Caused by: java.io.FileNotFoundException: C:\Documents%20and%20Settings\gzoller\My%20Documents\libs\JBoss%20ESB%204.2\samples\quickstarts\
    helloworld\jbossesb-listener.xml (The system cannot find the path specified)
    [java] at java.io.FileOutputStream.open(Native Method)
    [java] at java.io.FileOutputStream.init(FileOutputStream.java:179)
    [java] at java.io.FileOutputStream.init(FileOutputStream.java:70)
    [java] at org.apache.xalan.transformer.TransformerIdentityImpl.createResultContentHandler(TransformerIdentityImpl.java:286)
    [java] ... 11 more
    [java] at org.jboss.soa.esb.listeners.StandAloneBootStrapper.init(StandAloneBootStrapper.java:132)
    [java] at org.jboss.soa.esb.listeners.StandAloneBootStrapper.init(StandAloneBootStrapper.java:108)
    [java] at org.jboss.soa.esb.listeners.StandAloneBootStrapper.main(StandAloneBootStrapper.java:77)

    DB:3.64:Helloworld Exceptions mm


    You shouldn't have any problems installing JBoss Messaging 1.3.0GA into JBossAS 4.2. If that's not the case then check on the JBM forum because the team really wants your feedback. Seemless AS 4.2 integration is high on their priority list.

  • RELEVANCY SCORE 3.58

    DB:3.58:Error Running Samples/Quickstarts/Helloworld kx



    I followed the steps in the "Getting Started Guide" of JBoss ESB.When i ran the samples/quickstarts/helloworld example,I ran into this error -Any idea what am i missing here?*******************samples\quickstarts\helloworld\jbossesb.xml [java] javax.naming.NameNotFoundException: InquiryService not bound [java] at org.apache.ws.scout.transport.RMITransport.send(RMITransport.java:91) [java] at org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImp*******************E:\karthik\software\JBoss\jbossesb-4.0GA-bundle\samples\quickstarts\helloworldantBuildfile: build.xmlprepare:compile:jars: [delete] Deleting: E:\karthik\software\JBoss\jbossesb-4.0GA-bundle\samples\quickstarts\helloworld\build\Quickstart_helloworld.jar [jar] Building jar: E:\karthik\software\JBoss\jbossesb-4.0GA-bundle\samples\quickstarts\helloworld\build\Quickstart_helloworld.jarrun: [echo] Basic JMS Gateway and Listener with Actions [java] +----------------------------------------------------------+ [java] | | [java] | Starting JBossESB... | [java] | | [java] +----------------------------------------------------------+ [java] Reading config from E:\karthik\software\JBoss\jbossesb-4.0GA-bundle\samples\quickstarts\helloworld\jbossesb.xml [java] javax.naming.NameNotFoundException: InquiryService not bound [java] at org.apache.ws.scout.transport.RMITransport.send(RMITransport.java:91) [java] at org.apache.ws.scout.registry.RegistryImpl.execute(RegistryImpl.java:273) [java] at org.apache.ws.scout.registry.RegistryImpl.findService(RegistryImpl.java:736) [java] at org.apache.ws.scout.registry.BusinessQueryManagerImpl.findServices(BusinessQueryManagerImpl.java:638)thanks,Karthik

    DB:3.58:Error Running Samples/Quickstarts/Helloworld kx


    Helloworld "ant run" must have an ESB Server running on localhost.The ESB Server can be run standalone or as embedded in the JBoss Application Server."ant run" then makes a connection via RMI to the registry hosted in the ESB Server.Burr

  • RELEVANCY SCORE 3.56

    DB:3.56:Best Book For Jboss Esb? dk


    I have started going through the Jboss ESB. Can you guys recommend me which is the best book for Jboss ESB ?

    DB:3.56:Best Book For Jboss Esb? dk

    I am not aware of a book on Jboss ESB.

  • RELEVANCY SCORE 3.56

    DB:3.56:Jboss Esb On Jboss5 As dj



    Hi,has anyone already managed to installed the JBoss ESB on the new JBoss AS (Version 5) ? I'm getting an Error saying "Could not determine JMS provider". When I try to build it with ANT.I tried it with JBoss AS 5.0.0 and JBoss ESB 4.4Any suggestions? Thank you.Bye,John

    DB:3.56:Jboss Esb On Jboss5 As dj


    Sorry, no progress yet. We had a f2f this week and, with the upcoming holiday season, are unlikely to get much done before the New Year.I have created a task for this though, please watch it for further updates.https://jira.jboss.org/jira/browse/JBESB-2245

  • RELEVANCY SCORE 3.55

    DB:3.55:How To Import The Quickstarts In Jboss Developer Studio? sp



    I want to use the quickstart examples in JBoss Developer Studio.

    How must I import them?

    Thanks for your help

    Simon

    DB:3.55:How To Import The Quickstarts In Jboss Developer Studio? sp


    I found the problem.

    It's a firewall thing in our company.

    Thanks for help anyway.

  • RELEVANCY SCORE 3.55

    DB:3.55:Download Link For Quickstarts Is Not To Be Found d1



    I have looked every possible page around here.

    http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/

    and

    http://www.jboss.org/jbossas/downloads/

    The download link on the later takes to

    http://www.jboss.org/jdf/quickstarts/get-started/

    Again, that leads to nowhere if you are looking for the zip download.

    Is there any other place to download Quickstarts??

    DB:3.55:Download Link For Quickstarts Is Not To Be Found d1


    How about on http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/? Click "Get the Source" and choose to download the source zip file.

  • RELEVANCY SCORE 3.55

    DB:3.55:Initial Code For Publishing Web Service As Web Service jz



    Hi all , I wrote the initial code for publishing esb service as web service and committed into my branch(https://svn.labs.jboss.org/labs/jbossesb/workspace/jimma/) for your review. There is also a sample named helloworld_pub_service in quickstarts directory for it . When execute "ant deploy" under quickstarts/helloworld_pub_service , jboss will spit up these deployment message :
    17:43:33,000 INFO [JBoss4ESBDeployer] create esb service, Quickstart_helloworld_pub_service.esb

    17:43:33,035 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_esb] started, fullSize=200000, pageSize=2000, downCacheSize=2000

    17:43:33,041 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_gw] started, fullSize=200000, pageSize=2000, downCacheSize=2000

    17:43:33,362 INFO [JDBCDataStore] Generated token 'authToken:DB3B49D0-379A-11DD-BD9B-D7235840313A' for user: 'jbossesb/JBoss ESB User'

    17:43:33,383 INFO [JDBCDataStore] Generated token 'authToken:DB3E5710-379A-11DD-BD9B-9B9F5C506F1D' for user: 'jbossesb/JBoss ESB User'

    17:43:33,477 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

    17:43:38,606 INFO [DefaultEndpointRegistry] register: jboss.ws:context=firstserviceesb-simplelistener,endpoint=SimpleListener

    17:43:38,625 INFO [TomcatDeployer] deploy, ctxPath=/firstserviceesb-simplelistener, warUrl=.../tmp/deploy/tmp33655firstserviceesb-simplelistener-exp.war/

    17:43:39,206 INFO [WSDLFilePublisher] WSDL published to: file:/project/jbossesb/workspace/jimma/product/build/jbossesb-server-4.3.GA/server/default/data/wsdl/firstserviceesb-simplelistener.war/firstserviceesb_simplelistener.wsdl

    DB:3.55:Initial Code For Publishing Web Service As Web Service jz


    Where is the code for generation/publishing of web service ? I don't see anywhere in the sample.Next sample publish_as_webservice_inonly quickstart sample doesn't work? Did anybody try WSDL after publishing? It fails.

  • RELEVANCY SCORE 3.54

    DB:3.54:Monitoring Esb, Jms, Etc a7



    Can RHQ be used to monitor ESB ( JBoss ESB, Business Activity Monitor, or SwitchYatd ?

    Can it also be used to monitor JMS ( HornetQ, ActiveMQ, etc ) ?

    DB:3.54:Monitoring Esb, Jms, Etc a7


    Yes to most of those. What and how depends on the specific plugins.

    Switchyard isn't there yet, but will be later this year.

  • RELEVANCY SCORE 3.53

    DB:3.53:Should I Use Jboss As 4.2.0+Jbss Esb 4.2 + Active Bpel 5.0.2 3s



    hi,all.I am totally new to jboss esb and active BPEL. I want to use the ActiveBPEL BPEL Engine to orchestrate business process flow through JBoss ESB.I have download the active bpel quickstarts. But the trouble is from its docs and readmes, I can't get the right version of jboss esb, active bpel and jboss as.I just guess should I use JBOSS AS 4.2.0+JBSS ESB 4.2 + active BPEL 5.0.2? Thank you very much for the reply.

    DB:3.53:Should I Use Jboss As 4.2.0+Jbss Esb 4.2 + Active Bpel 5.0.2 3s


    yes,thanks.This problem has been solved, it's because I haven't set a proper value oforder.approval.drop.location' property in 'webservice_bpel/services/order-manager/order-manager.properties.the webservice_bpel runs very well now. Thank you very much.

  • RELEVANCY SCORE 3.51

    DB:3.51:Jbossesb 4.2ga Quickstart Issues f7



    Hi, I am trying to evaluate the JBoss ESB product and upon installation am running into issues trying to following the "Getting Started" trail. I am unable to run the basis hello world module.When I attempt to follow the instructions (both for the standalone and the esb archive mode) I get the following error. Any help or guidance would be much appreciated.Thanks.--- ERROR DETAILS ---[C:/home/install/jboss/jbossesb-server-4.2MR2/samples/quickstarts/helloworld] ant undeploy-jms-destsBuildfile: build.xmlBUILD FAILEDC:\home\install\jboss\jbossesb-server-4.2MR2\samples\quickstarts\helloworld\build.xml:9: The following error occurred while executing this line:C:\home\install\jboss\jbossesb-server-4.2MR2\samples\quickstarts\conf\base-build.xml:26: JBossESB must be built. Please run 'ant' in C:\home\install\jboss\jbossesb-server-4.2MR2Total time: 0 seconds

    DB:3.51:Jbossesb 4.2ga Quickstart Issues f7


    Can you post the contents of the report file for that test? It's in product/services/soapui-client/target/test-reports

  • RELEVANCY SCORE 3.50

    DB:3.50:Urgent Help Please : Actionprocessingpipeline] Failed To Sen kx



    Hi JBoss team, I am trying to have two providers like jms-provider and fs-provider in signle jboss-esb and both are not dependent on each other.fs-provider just reads a file from directory and try to post to a queue.This example i pikced from samples section.I get the follwoing exception below when i start esb in standalone mode. Please help.....[java] 22:35:45,125 INFO [main][SmooksTransformer] All Smooks configurations are now loaded. [java] Body: Hello World In A File [java] 22:36:03,343 INFO [pool-2-thread-1][SmooksTransformer] RegisteringJBoss ESB Message-Exchange as Smooks Useragent: [from-type:text/xml:partsOrder:from:Parts123:OrderDispatchService:to-type:text/xml:postOrder:to:ERP_1:PartSalesOrderService]. Profiles: [[from-type:text/xml:partsOrder, from:Parts123:OrderDispatchService, to-type:text/xml:postOrder, to:ERP_1:PartSalesOrderService]] [java] [Fatal Error] :1:1: Content is not allowed in prolog. [java] 22:36:03,421 ERROR [pool-2-thread-1][ActionProcessingPipeline] Failed to send error to address null. [java] org.jboss.soa.esb.couriers.CourierException: No deliverAsync courier[java] at jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:166) [java] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.faultTo(ActionProcessingPipeline.java:436) [java] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:287) [java] at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:301) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) [java] at java.lang.Thread.run(Thread.java:595)jms-provider name="JBossMQ" connection-factory="WSMQQueueConnectionFactory" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-URL="localhost" jms-bus busid="bluebirdGwChannel" jms-message-filter dest-type="QUEUE" dest-name="wsmq/parts123_transform_gw"/ /jms-busjms-bus busid="bluebirdEsbChannel" jms-message-filter dest-type="QUEUE" dest-name="wsmq/parts123_transform_esb"/ /jms-bus jms-bus busid="quickstartGwChannel"jms-message-filter dest-type="QUEUE" dest-name="wsmq/parts123_xml_transform_gw" / /jms-busjms-bus busid="quickstartEsbChannel"jms-message-filter dest-type="QUEUE" dest-name="wsmq/parts123_xml_transform_esb" / /jms-busjms-bus busid="quickstartGwChannel"jms-message-filter dest-type="QUEUE" dest-name="wsmq/parts123_transform_Response" / /jms-bus jms-bus busid="filestartEsbChannel" jms-message-filter dest-type="QUEUE" name="wsmq/parts123_transform_Response"selector="type='fromHelloworldFileAction'"//jms-bus/jms-providerfs-provider name="FSprovider1"fs-bus busid="helloFileChannel" fs-message-filter directory="d:\jboss-esb\samples\quickstarts\helloworld_file_action\build\dirs\input"input-suffix=".dat" work-suffix=".esbWorking" post-delete="false" post-directory="d:\jboss-esb\samples\quickstarts\helloworld_file_action\build\dirs\output"post-suffix=".sentToEsb" error-delete="false" error-directory="d:\jboss-esb\samples\quickstarts\helloworld_file_action\build\dirs\error" error-suffix=".IN_ERROR"//fs-bus /fs-provider jms-listener name="JMS-Gateway"busidref="bluebirdGwChannel" maxThreads="1" is-gateway="true" /jms-listener name="jmsTransformer" busidref="bluebirdEsbChannel" maxThreads="1"/ fs-listener name="FileGateway" busidref="helloFileChannel" maxThreads="1" is-gateway="true" poll-frequency-seconds="1" / jms-listener name="helloWorldFileAction"busidref="filestartEsbChannel"maxThreads="1" /action name="displayBeforeTransformer"class="com.bluebird.integration.parts123.transformation.pojo.MyJMSListenerAction"process="displayMessage" / property name="from" Parts123:OrderDispatchService" /property to-type" value="text/xml:postOrder" /action convertPOJO2Message" class="com.bluebird.integration.Parts123Action" / action name="returnToSender"com.bluebird.integration.parts123.transformation.pojo.MyJMSListenerAction" process="sendResponse" /

    DB:3.50:Urgent Help Please : Actionprocessingpipeline] Failed To Sen kx


    How about you just zip up and email me the project?I'm assuming you followed the project structure of the quickstarts.Burr

  • RELEVANCY SCORE 3.46

    DB:3.46:Jbossesb Unit Test Result m7



    Hello,1. I downloaded jbossesb-server-4.2.1GA. Under \jbossesb-server-4.2.1GA\docs\tests, there is TESTS-TestSuites.txt. The link inside this file is not working.http://jboss.sourceforge.net/junit-results/32/2007-07-13.23-362. If I would like to run those unit test myself, what should I? I try to download the source jbossesb-4.2.1GA-src.zip. If I run "ant test" from the qa folder, will that run all the 4096 unit test as specified in TESTS-TestSuites.txt file?3. Do those unit tests include the sample applications (quickstarts and trailblazer)? I mean, if I run those unit test, do I still need to run sample applications?4. Last question: I want to know if those unit tests (or sample application, or JBoss ESB server) are instrumented with Emma code coverage?Too many questions :)...Bow to thank you!

    DB:3.46:Jbossesb Unit Test Result m7


    Could you run a quick test for me?Could you change the following line
    String actualListenerConfig = configUtil.getListenerConfig("simple-schedule-listener").toXml();

  • RELEVANCY SCORE 3.46

    DB:3.46:Documentation Incorrect In Jbossesb-4.2mr1 77



    Hi, I have just downloaded the jbossesb-4.2MR1 and the associated documentation.It appears that the documenation is'nt correct (unless I have done a serious mistake). An instance where I find it incorrect is:The doc says copy the esb-quickstart-service.xml from ../samples/quickstarts .... However, if I go to the samples/quickstarts folder I dont find the file esb-quickstart-service.xml, instead I see two files named esb-quickstart-jbmq-service.xml and esb-quickstart-jbm-service.xml.Could someone please help on what might be going wrong with my observation.

  • RELEVANCY SCORE 3.44

    DB:3.44:Native Services In Esb pf



    Question on terminology: what is the difference between a native service and non-native service on ESB?In a document we all know and love, it states that a native service is one which is currently identified in the jboss-esb.xml, and that a service so defined is 'directly' hosted. This is clear for services whose actions are implementations of classes deployed on the ESB (AS version or ESB server version).No proxies are used in performing actions.But for example in the webservice quickstarts, a webservice is deployed independently of the corresponding ESB service, and accessed from the ESB service from within an action of the service via org.jboss.soa.esb.actions.soap.SOAPClient.Is this form of access viewed as access by proxy or not? Or in other words, is this webservice native or non-native?* If not, what is the procedure for accessing an external webservice via proxy from within an action.* If it is, then are all web services accessed via ESB considered non-native?

    DB:3.44:Native Services In Esb pf


    Not really. EJBs can be handled via their remote interface therefore can be local or remote. Spring has its own action that assumes it is local.By "local" I mean in the same container/JVM.We do have quickstarts for both SLSB and Spring POJOs that demonstrate how to interact. So while not the same exact technique it is close. The difference is that with SOAP/XML you can essentially generate a client on the fly. With Spring EJB that is a little bit harder.Burr

  • RELEVANCY SCORE 3.43

    DB:3.43:Jboss Esb And 64bit 9f



    Has anyone tried running ESB 4.7 or 4.6 using 64bit windows, 64bit java and jboss 5.1.0 GA?

    Nikos.

    DB:3.43:Jboss Esb And 64bit 9f


    Hi Ryan,

    thanks for fast reply.

    @Daniel: Is there also an "official" statement regarding running JBossESB 4.4 within 32Bit / 64Bit JVM on Windows 64Bit OS?

    Br,

    Dennis

  • RELEVANCY SCORE 3.42

    DB:3.42:Error With Quickstart Bpm_Orchestration4 km



    I am using jbossesb-server-4.9 (and tried jboss-soa-p-5 and got same error).

    Fresh install .. start the server ... go to C:\jbossesb-server-4.9\samples\quickstarts\bpm_orchestration4 and type "ant deploy".

    I get the following on the console ...

    11:45:29,151 WARN [ServiceController] Problem starting service jboss.esb:deployment=Quickstart_bpm_orchestration4.esb
    java.lang.NoClassDefFoundError: AbstractActionPipelineProcessor

    at java.lang.ClassLoader.defineClass1(

    )

    See attached log.

    Other quickstarts work fine.

    DB:3.42:Error With Quickstart Bpm_Orchestration4 km


    Removing the working directories did not help. I downloaded jbossesb-server-4.10 and the bpm_orchestration4 quickstart worked fine out of the box. I have not done any comparison to see what is different. I have not tried a new or different version of soa 5.1 to see if it is now working and fixed there or still broke.

  • RELEVANCY SCORE 3.42

    DB:3.42:Jboss 6.1 Esb 4.10 Soapproxy Doen't Work With Http Basic Auth! c7



    I have esb service action:

    action name="proxy" class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"

    property name="wsdl" value="http://localhost:8081/myservice?wsdl"

    /property

    /action

    It works fine. But web service aks for HTTP Basic authentification.

    By documentation, i create http.properties:

    # AuthBASIC config

    configurators=AuthBASIC

    # AuthBASIC config

    auth-username=XXX

    auth-password=XXX

    authscope-host=localhost

    authscope-port=8080

    And made changes in jboss-esb.xml:

    action name="proxy" class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"

    property name="wsdl" value="http://localhost:8081/myservice?wsdl"/

    property name="endpointUrl" value="http://localhost:8081/myservice"/

    property name="file" value="/META-INF/http.properties"/ //

    property name="clientCredentialsRequired" value="true"/

    /action

    1. In tutorials and quickstarts - HTTPS, e.g. SSL service with BASIC auth, and probably it works fine. BUT I need HTTP without SSL.

    2. After adding this property:

    property name="file" value="/META-INF/http.properties"/

    I always have deployment error: host parameter is null.

    Have anybody some experiance with ESB SOAPProxy and basic auth ?

    (Throught SoapUI - with Basic credentials - my service works fine!)

    DB:3.42:Jboss 6.1 Esb 4.10 Soapproxy Doen't Work With Http Basic Auth! c7


    Hi everybody,

    I've a problem that related to this topic. Please visit https://community.jboss.org/thread/204590

    Thanks

  • RELEVANCY SCORE 3.41

    DB:3.41:Problem Running Hello World Quickstart - Jbossesb-4.2mr1 8z



    Hey everyone, I think that I'm close to getting this work work - but I'm missing something basic - can anyone suggest what's wrong?Many thanks,Len DiMaggioldimaggi@redhat.comSo far, I've:1) Installed jbossesb-4.2 (from src: jbossesb-4.2MR1-src.zip) into /opt/jbossesb-4.22) Installed jboss-4.0.5.GA (from src: jboss-4.0.5.GA-src.tar.gz) into /opt/jboss-4.0.5.GA-src, built server3) Created /opt/jbossesb-4.2/product/install/deployment.properties and set: org.jboss.esb.dist.lib=../build/jbossesb/lib4) In /opt/jbossesb-4.2/product, ran ant dist5) Verifed that ESB standalone started up - /opt/jbossesb-4.2/product/build/jbossesb-server-4.2.MR1/bin/run.sh -c default then shut it down6) Started jboss-4.0.5.GA - /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/bin/run.sh -c default7) Copied jbossesb.sar to jboss-4.0.5.GA cp -pR /opt/jbossesb-4.2/product/build/jbossesb/lib/jbossesb.sar /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/default/deploy/8) Modified /opt/jbossesb-4.2/product/samples/quickstarts/quickstarts.properties and set: esb.product.lib.dir=../../../../product/build/jbossesb/lib/ jbosshome.dir=/opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/9) Copied /opt/jbossesb-4.2/product/samples/quickstarts/esb-quickstart-jbmq-service.xml to /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/default/deploy/ - no errors - saw this in the server log:12:00:10,402 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=juddiDB' to JNDI name 'java:juddiDB'12:00:10,406 INFO [DatabaseInitializer] Initializing java:/juddiDB from listed sql files12:00:10,558 INFO [JuddiRMIService] starting juddi RMI service12:00:11,782 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=JBossESBDS' to JNDI name 'java:JBossESBDS'12:00:11,784 INFO [DatabaseInitializer] Initializing java:/JBossESBDS from listed sql files10) Ran ant in /opt/jbossesb-4.2/product/samples/quickstarts/helloworld - saw these results - and Quickstart_helloworld.esb in opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/default/deployBuildfile: build.xmlclean: [delete] Deleting directory /opt/jbossesb-4.2/product/samples/quickstarts/helloworld/buildcompile: [mkdir] Created dir: /opt/jbossesb-4.2/product/samples/quickstarts/helloworld/build/classes [javac] Compiling 3 source files to /opt/jbossesb-4.2/product/samples/quickstarts/helloworld/build/classesruntest: [echo] Runs Test JMS Sender [java] Connection StartedBUILD SUCCESSFUL11) Saw same results with ant runtest12) Tried ant deploy - saw these errors in server log:13:05:48,318 ERROR [MainDeployer] Could not create deployment: file:/opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/default/tmp/deploy/tmp30414Quickstart_helloworld.esb-contents/jbm-queue-service.xmlorg.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.jms.server.destination.QueueService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.server.destination.QueueService)14) Tried to clear up class not found by - thrashing, basically: cp -p /opt/jbossesb-4.2/product/build/jbossesb/lib/ext/jboss-messaging-client.jar /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/default/lib cp -p /opt/jbossesb-4.2/product/build/jbossesb/lib/ext/jboss-jmx.jar /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/default/lib cp -p /opt/jbossesb-4.2/product/build/jbossesb/lib/ext/jbossall-client.jar /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/default/lib15) Hit this exception:Deployment FAILED reason: no protocol: xmdesc/Queue-xmbean.xml; - nested throwable: (java.net.MalformedURLException: no protocol: xmdesc/Queue-xmbean.xml)16) Out of ideas - Do I need the JBoss Messaging Server to run the samples?

    DB:3.41:Problem Running Hello World Quickstart - Jbossesb-4.2mr1 8z


    Thanks everyone - 'got it working:1) Installed jbossesb-4.2 (from src: jbossesb-4.2MR1-src.zip) into /opt/jbossesb-4.22) Installed jboss-4.0.5.GA (from src: jboss-4.0.5.GA-src.tar.gz) into /opt/jboss-4.0.5.GA-src, built server3) Created /opt/jbossesb-4.2/product/install/deployment.properties and set: org.jboss.esb.dist.lib=../build/jbossesb/lib4) In /opt/jbossesb-4.2/product, ran ant dist5) Verifed that ESB standalone started up - /opt/jbossesb-4.2/product/build/jbossesb-server-4.2.MR1/bin/run.sh -c default then shut it down6) Started jboss-4.0.5.GA - /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/bin/run.sh -c default7) Installed jboss-messaging (from jboss-messaging-1.2.0.SP1-src.zip) into /opt/jboss-messaging/jboss-messaging-1.2.0.sp1-src per http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.2.0.GA/html/installation.html#install4/opt/apache-ant-1.7.0/bin/ant -f release-admin.xml8) Modified /opt/jbossesb-4.2/product/samples/quickstarts/quickstarts.properties and set: esb.product.lib.dir=../../../../product/build/jbossesb/lib/ jbosshome.dir=/opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/9) Copied /opt/jbossesb-4.2/product/samples/quickstarts/esb-quickstart-jbm-service.xml to /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/messaging/deploy/10) Copied /opt/jbossesb-4.2/product/samples/quickstarts/helloworld/build/Quickstart_helloworld.esb to /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/messaging/deploy/11) Copied jbossesb.sar to jboss-4.0.5.GA cp -pR /opt/jbossesb-4.2/product/build/jbossesb/lib/jbossesb.sar /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/messaging/deploy/cp -pR /opt/jbossesb-4.2/product/build/jbossesb/lib/jbossesb.sar /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/messaging/deploy/;cp /opt/jbossesb-4.2/product/samples/quickstarts/esb-quickstart-jbm-service.xml /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/messaging/deploy/;cp /opt/jbossesb-4.2/product/samples/quickstarts/helloworld/build/Quickstart_helloworld.esb /opt/jboss-4.0.5.GA-src/build/output/jboss-4.0.5.GA/server/messaging/deploy/12) Edited /opt/jbossesb-4.2/product/samples/quickstarts/helloworld/base-build.xml[ldimaggi@ldimaggi helloworld]$ diff base-build.xml base-build.xml.orig !-- Required for JMS Client Code. -- !-- Required for JMS Client Code. --12) ant runtest

  • RELEVANCY SCORE 3.41

    DB:3.41:Running Jbossesb From Within The Jbosside - Example Cannot B 39



    Hello EverybodyI am new to JBossESB and to quickly get an impression I tried to make running the Quick start Hello World example described at link "Running JBossESB from within the JBossIDE". I used exactly the same versions of JBossIDE and JBossESB boundles as recommended and I cannot even build the project because of errors like:The declared package "org.jboss.soa.esb.dvdstore" does not match the expected package "samples.quickstarts.aggregator.src.org.jboss.soa.esb.dvdstore"in samples\quickstarts\aggregator\src\org\jboss\soa\esb\dvdstore\Customer.javaor in many files:The import org.jboss.soa.esb.actions cannot be resolvedI could try one by one correct the errors but maybe there is a simplest way of doing it? Did anybody go through this tutorial successfully?thxDarek

  • RELEVANCY SCORE 3.41

    DB:3.41:Jboss Esb Can't Run Helloworld Sample Application fp



    I'm really lost and need a little help here, i'm trying to configure a JBoss ESB Server on a Windows 7, i'm pretty new to jboss esb and jboss itself.. and not much of a java guru... all i wan't to do is run a sample test application like a "helloworld" to see everything is working fine. And i can't even do that... i run "ant deploy" on samples\quickstarts\helloworld and it says is deployed correctly... but then i try to run "ant runtest" from the same directory and i have an ugly exception....

    DB:3.41:Jboss Esb Can't Run Helloworld Sample Application fp


    i think that the problem is that i'm trying to run jboss as 7 along with jboss esb, but i don't know how to deploy directly to the jboss as 7... but if i run directly the jboss esb it works. Launching from the command line bin/run.bat.

    How do you deploy to the jboss as 7?

  • RELEVANCY SCORE 3.40

    DB:3.40:Jboss Esb And Ws-Atomictransaction 1a



    Hi,

    Does Jboss ESB support WS-AtomicTransaction ?

    DB:3.40:Jboss Esb And Ws-Atomictransaction 1a


    Hi,

    Does Jboss ESB support WS-AtomicTransaction ?

  • RELEVANCY SCORE 3.39

    DB:3.39:Run Jboss Esb On Tomcat fs



    Hi,I wonder does anyone tried to deploy jboss esb on tomcat using jbpm and some esb services.Thanks in advanceVlad.

    DB:3.39:Run Jboss Esb On Tomcat fs


    I successfully build war file and deploy on tomcat.But I found out that this web application uses some system properties for starting. I mean class org.jboss.soa.esb.servlet.ConfigListener. I concern only how my changes can affect other packages which are used by jboss esb.I also found if I need to deploy 2 or more esb services I need to run to web applications: one war - one esb.Does anyone run more than one esb service on tomcat?And what I lost if I use tomcat instead of jboss esb server?Regards,Vlad

  • RELEVANCY SCORE 3.39

    DB:3.39:Esb Serviceinvoker Does Not Work x3



    I tried to run JBoss ESB 4.7 quickstarts in SOA-p 5.0 which contains ESB4.7 runtime, if I try to send an ESB message to test the deployed esb service, it fail every time, take *Helloworld *quickstart as an example, after I deployed it to SOA-P 5.0 successfully, I tried to run SendJMSMessage, it work fine, but when I tried to run SendESBMessage with serviceCategory=FirstServiceESB, serviceName=SimpleListener , it failed with the following excaption:

    Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:545) at org.jboss.soa.esb.client.ServiceInvoker.init(ServiceInvoker.java:174) at org.jboss.soa.esb.client.ServiceInvoker.init(ServiceInvoker.java:155) at org.jboss.soa.esb.client.ServiceInvoker.init(ServiceInvoker.java:197) at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage.main(SendEsbMessage.java:55)Caused by: org.jboss.soa.esb.services.registry.RegistryException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:341) at org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor.findEPRs(InVMRegistryInterceptor.java:85) at org.jboss.soa.esb.services.registry.RegistryFactory$HeadRegistryInterceptor.findEPRs(RegistryFactory.java:229) at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226) at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:532) ... 4 moreCaused by: javax.xml.registry.JAXRException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException at org.apache.ws.scout.registry.BusinessQueryManagerV3Impl.findConcepts(BusinessQueryManagerV3Impl.java:516) at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.getJBossESBTModel(JAXRRegistryImpl.java:646) at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:300) ... 8 more

    I also checked the ESB-console, the service "FirstServiceESB:SimpleListener" list there, doesn't the ServiceInvoker work for ESB4.7 or SOA-P 5.0?

    Thanks, Denny

    DB:3.39:Esb Serviceinvoker Does Not Work x3

    Daniel, I don't find a security provider named org.bouncycastle.jce.provider.BouncyCastleProvider in the java.security file. I run the "helloworld" quickstart on two different PC , one is on Fedora 10 and another is Fedora 8, they both get the same error as described :https://jira.jboss.org/jira/browse/SOA-1864, just now, I tried to run the test on Vista, it works without errors, it seems something wrong with my Linux environment.

  • RELEVANCY SCORE 3.38

    DB:3.38:Jboss Esb 5.X - Helloworld Quickstart Deployment Issues - Failed To Find Action Class 8z



    Hi,

    I have just started to exploring jboss esb , I have downloaded jboss soa 5.x platform on Windows 7 machine with Developer studio 4.1 and started with samples provided by jboss quickstarts.

    When I deploy helloworld on App server, it gives this error.

    Caused by: java.lang.RuntimeException: Failed to find action class 'org.jboss.soa.esb.samples.quickstart.helloworld.MyJMSListenerAction'.

    I see two runtime 1. JBoss ESB runtime ( which has the jbossesb-rosetta.jar" ) and 2. Jboss EAP 5.x runtime ( it does not have jbossesb-rosetta.jar")

    I have also added in the external jar file as well, but no luck.. Can you guys let me know I am missing to run the sample?

    appriciated your help..

    Thanks

    Kali

    DB:3.38:Jboss Esb 5.X - Helloworld Quickstart Deployment Issues - Failed To Find Action Class 8z


    Fixed it. Deployment configuration issue... Have these two files in your .setting folder and deploy. It worked for me...

    .settings Folder...

    File1: org.eclipse.wst.common.component

    ?xml version="1.0" encoding="UTF-8"?

    project-modules id="moduleCoreId" project-version="1.5.0"

    wb-module deploy-name="Chapter3" (Change to your deployment name)

    wb-resource deploy-path="/" source-path="/src"/

    wb-resource deploy-path="/" source-path="/esbcontent"/

    property name="java-output-path" value="/esbcontent/build/classes/"/

    /wb-module

    /project-modules

    File2: org.eclipse.wst.common.project.facet.core

    ?xml version="1.0" encoding="UTF-8"?

    faceted-project

    runtime name="jboss-5.1.0.GA Runtime"/

    fixed facet="jst.java"/

    fixed facet="jst.jboss.esb"/

    installed facet="jst.jboss.esb" version="4.4"/

    installed facet="jst.java" version="6.0"/

    /faceted-project

  • RELEVANCY SCORE 3.37

    DB:3.37:Problem With Webservice_Producer Quickstart p3



    Hello,I am trying to run the webservice_quickstart sample but when i type ant runtest after the deployment i get the following errorsaygoodbye_over_http: [echo] Invoking a JBossWS Endpoint over HTTP (via JBoss ESB). [java] Calling JBoss Remoting Listener using locator URI: http://localhost:8765 [java] Exception in thread "main" org.jboss.remoting.CannotConnectException: Can not connect http client invoker. [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:201) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81) [java] at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) [java] at org.jboss.remoting.Client.invoke(Client.java:525) [java] at org.jboss.remoting.Client.invoke(Client.java:488) [java] at org.jboss.remoting.Client.invoke(Client.java:473) [java] at org.jboss.soa.esb.samples.quickstart.webserviceproducer.test.SendMessage.sendMessageToJBRListener(SendMessage.java:72) [java] at org.jboss.soa.esb.samples.quickstart.webserviceproducer.test.SendMessage.main(SendMessage.java:113) [java] Caused by: java.net.ConnectException: Connection refused: connect [java] at java.net.PlainSocketImpl.socketConnect(Native Method) [java] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) [java] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) [java] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) [java] at java.net.Socket.connect(Socket.java:519) [java] at java.net.Socket.connect(Socket.java:469) [java] at sun.net.NetworkClient.doConnect(NetworkClient.java:157) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:382) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:509) [java] at sun.net.www.http.HttpClient.(HttpClient.java:231) [java] at sun.net.www.http.HttpClient.New(HttpClient.java:304) [java] at sun.net.www.http.HttpClient.New(HttpClient.java:316) [java] at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813) [java] at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765) [java] at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690) [java] at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:857) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:163) [java] ... 7 moreBUILD FAILEDC:\Stage_jboss\jbossesb-4.2MR3\samples\quickstarts\webservice_producer\build.xml:32: The following error occurred while executing this line:C:\Stage_jboss\jbossesb-4.2MR3\samples\quickstarts\webservice_producer\build.xml:46: Java returned: 1have someone faced this problem before?m_rad

    DB:3.37:Problem With Webservice_Producer Quickstart p3


    Yes It was running and it didn't notify any error

  • RELEVANCY SCORE 3.37

    DB:3.37:How To Call From Non-Switchyard Application Without Http Protocol z9



    I'm researching a proper Switchyard API which corresponds to ServiceInvoker provided by JBossESB. I've alread read a forum[1] and understood that @Reference and RemoteInvoker are very useful tools for us, however I found a scenario which can't be covered by those tools. Is there any API that can be called in non-SwitchYard Apprication without HTTP protcol?

    For example, a quickstartof native-client[2] in JBossESB, ServiceInvoker is called in WAR Application, and ServiceInvoker doesn't use HTTP protocol to invoke a ESBservice.

    [1] Switchyard Equivalent ofJBossESB's ServiceInvoker?

    https://community.jboss.org/message/821122#821122

    [2]native-clientinJBossESBquickstarts

    http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_2/product/samples/quickstarts/native_client/war/src/org/jboss/soa/esb/samples/quickstart/nativeclient/webservice/HelloWorldWS.java

    Thanks.

    DB:3.37:How To Call From Non-Switchyard Application Without Http Protocol z9


    Thanks Keith!

    I've logged the following JIRA feature request as [#SWITCHYARD-1678] Need feature to call from non-SwitchYard Application without HTTP protocol - JBoss Issue Tracker .

  • RELEVANCY SCORE 3.35

    DB:3.35:Help Needed On Schedulers In Jboss Esb p8



    Hi,

    Here is my requirement, i need to poll the Data Base Table for every 10 seconds.If there is any new data inserted by external systems in the table, then i need to Inject certain Beans Using spring beans xml. For this Requirement i have gone through the "ScheduledEventMessageComposer" illustrated in the Quick Started Samples(\soa-p-5.3.0.GA\jboss-soa-p-5\jboss-as\samples\quickstarts\scheduled_services). Can any one suggest me where can i find more Documentation and Samples on Schedulers ?

    DB:3.35:Help Needed On Schedulers In Jboss Esb p8


    Hi,

    you can also check the Notifier component. i think there is one notifier to moniter the db table dml opertaions. using this you can send the notification alert when ever any changes in db table.

  • RELEVANCY SCORE 3.33

    DB:3.33:Jboss Esb And Maven 9x



    I am about to embark on a ESB based project, I would like to use maven. I notice that there is an ESB plugin for maven, however I can't find any examples and there is very little documentation.

    It would be great if the ESB samples (samples/quickstarts) contained a pom.xml...

    Does anyone have or know of some good examples? Are there any plans to include maven builds in the quick starts or even the trailblazer?

    DB:3.33:Jboss Esb And Maven 9x


    Hi Richard,

    Thanks very much for the response, appreciate it. In the mean time I have done an investigation and come up with a solution. I have posted it as an article (http://community.jboss.org/wiki/JBossESBTrailblazerbuildingwithMaven2).

    I would appreciate some additions to it though, so please feel free to contribute/correct if you have time.

  • RELEVANCY SCORE 3.33

    DB:3.33:Jboss Esb Downloads xj



    Both downloads and document sections of JBoss ESB are broken. They just displays "Not found".Thanks.

    DB:3.33:Jboss Esb Downloads xj


    Both downloads and document sections of JBoss ESB are broken. They just displays "Not found".Thanks.

  • RELEVANCY SCORE 3.32

    DB:3.32:Confusion On Jboss Soa And Jboss Esb??? xp



    I few weeks earlier, i had been trained on Jboss SOA. Does it mean that i am automatically trained on Jboss ESB as well???

    DB:3.32:Confusion On Jboss Soa And Jboss Esb??? xp


    Hey Jeff,

    I seem to have misplaced your email id. However if u confirm this is the one i can contact you directly. Is it jdelong@redhat.com

    Thanks

  • RELEVANCY SCORE 3.32

    DB:3.32:Http Client In Jboss Esb dc



    I am working with jboss-soa-p.4.2.0 which consists of JBoss ESB 4.2.1 GA. I want to develop an Http client for ESB, i.e. i need to invoke any esb service via an http request.How should i go about this? Is there any sample or could anyonne refer to some documentation in this regard?

    DB:3.32:Http Client In Jboss Esb dc


    Hi,
    i need to invoke any esb service via an http request.well depending on your requirements you could perhaps configure a JBossRemoting gateway. See the webservice_producer quickstart for information about how to configure it. If that does not meet your needs you could create a simpel servlet that uses the ServiceInvoker to call a service in the ESB. You could extract the service category and service name from the request or perhaps configure that information in web.xml. Would one of those solutions work for you situation? Regards, /Daniel

  • RELEVANCY SCORE 3.32

    DB:3.32:I'M Not Able To Compile The Samples In My Evaluation Copy The Standalone Soa. m9



    Here's the compiler error:

    [javac] C:\jboss\jboss-soa-p-standalone.5.0.0\jboss-esb\samples\quickstarts\helloworld\src\org\jboss\soa\esb\samples\quickstart\helloworld\MyJMSListenerAction.java:23: cannot access org.jboss.soa.esb.actions.AbstractActionLifecycle [javac] bad class file: C:\jboss\jboss-soa-p-standalone.5.0.0\jboss-esb\server\default\deployers\esb.deployer\lib\jbossesb-rosetta.jar(org/jboss/soa/esb/actions/AbstractActionLifecycle.class) [javac] class file has wrong version 50.0, should be 49.0

    Is anyone able to shed some light on this problem for me?

    I can't proceed with the eval.

    Thanks,

    Johnny H

    DB:3.32:I'M Not Able To Compile The Samples In My Evaluation Copy The Standalone Soa. m9


    Thanks Kevin,

    No support on this eval I'm afraid. So, I'll give your suggestion a go.

    Thanks very much.

    Cheers,

    John

  • RELEVANCY SCORE 3.30

    DB:3.30:Integration With Jbpm j3



    Hi,Are there any instructions on integrating JBoss jBPM with JBoss ESB? Are there any plans to offer jBPM as a JBoss ESB service?Thanks and Regards,Barry

    DB:3.30:Integration With Jbpm j3


    Thank you so much for such a great response!!

  • RELEVANCY SCORE 3.30

    DB:3.30:File Listener / Gateway a3



    I am having a heck of a problem getting somethin in my config file working correctly. I have a similar service working in my config file already and I do not understand why this service will not work:

    fs-provider
    fs-bus busid="fromGSMOSChannel"
    fs-message-filter
    directory="C:\\dev\\projects\\esb\\jbossesb-42MR3\\samples\\quickstarts\\bpm_orchestration1\\build\\gsmos"
    input-suffix=".xml"
    post-delete="true"
    error-delete="false"
    /
    /fs-bus

    fs-bus busid="startFromGSMOSChannel"
    fs-message-filter
    directory="C:\\dev\\projects\\esb\\jbossesb-42MR3\\samples\\quickstarts\\bpm_orchestration1\\build\\gsmos"
    input-suffix=".deployProcessESB"
    post-delete="true"
    error-delete="false"
    /
    /fs-bus
    /fs-provider

    DB:3.30:File Listener / Gateway a3


    Hi Tom,Yes - I am using MR3 - to take a quick view at the code I just JAD'ed it.Thanks,Jason

  • RELEVANCY SCORE 3.30

    DB:3.30:Where Is The Login Quickstart Tutorial cx



    The JBoss AS 7 quickstart tutorial (https://docs.jboss.org/author/display/AS7/Login+quickstart) reads "Switch to the quickstarts/login directory".

    However no such folder exists:

    find jboss-as-quickstarts-7.1.1.CR2/ | grep login

    ... outputs nothing.

    DB:3.30:Where Is The Login Quickstart Tutorial cx


    That was for AS 7.0 and from what I know, it no longer exists. Take a look at the latest docs here https://docs.jboss.org/author/display/AS71/Quickstarts

  • RELEVANCY SCORE 3.29

    DB:3.29:Jboss Esb Server 4.11 Quickstarts Examples Deploy Error 1s



    Downloaded jbossesb-server-4.11 and placed it in local path D:\jboss\jbossesb-server-4.11

    Set the JBOSS_HOME to this path.

    Started jboss with he following command from shell: d:\jboss\jbossesb-server-4.11\bin.\run.bat -c default -b 0.0.0.0

    The server starts without errors or warnings.

    Then I configured the quickstart.properties file in the /conf directory located in D:\jboss\jbossesb-server-4.11\samples\quickstarts\conf

    Finally moved in D:\jboss\jbossesb-server-4.11\samples\quickstarts\helloworld

    and executed the command:D:\jboss\jbossesb-server-4.11\samples\quickstarts\helloworld ant deploy

    The execution terminates with the Build Error

    Here after I paste the execution output:

    Buildfile: D:\jboss\jbossesb-server-4.11\samples\quickstarts\helloworld\build.xml

    [echo] product.dir=D:\jboss\jbossesb-server-4.11

    [echo] default

    check-jbossesb-dist:

    qslib-dependencies:

    non-qslib-dependencies:

    jbossesb-quickstart-override:

    jbossesb-source-dependencies:

    jbossesb-server-dependencies:

    [echo] Using profile: default

    check-as-version:

    [echo] product.dir=D:\jboss\jbossesb-server-4.11

    [echo] server.server=D:\jboss\jbossesb-server-4.11\samples\quickstarts\helloworld\jbossjbossesb-server-4.11

    server\server\default

    jbossesb-dependencies-as4:

    jbossesb-dependencies-as5:

    messaging-config:

    messaging-dependencies:

    jbossmq-dependencies:

    hornetq-dependencies:

    quickstart-specific-dependencies:

    classpath-dependencies-as4:

    BUILD FAILED

    D:\jboss\jbossesb-server-4.11\samples\quickstarts\conf\base-build.xml:401: D:\jboss\jbossesb-server-4.11\samples

    \quickstarts\helloworld\jbossjbossesb-server-4.11server\client does not exist.

    Total time: 0 seconds

    What can I verify or change to solve this problem?

    It happens for each example available.

    DB:3.29:Jboss Esb Server 4.11 Quickstarts Examples Deploy Error 1s


    Thanks Tom

    starting from your question I found the deployment problem

    I was using the line in the quickstart.properties with backslashes in the path:

    org.jboss.esb.server.home=D:\jboss\jbossesb-server-4.11

    since it's running on a windows xp

    I simply changed the path with slashes:

    org.jboss.esb.server.home=D:/jboss/jbossesb-server-4.11

    now it works ....

    My quetion now is: "Why?"

  • RELEVANCY SCORE 3.29

    DB:3.29:Maven Plugin For Jboss Esb And Jbpm xf



    JBoss Team,Do you have out of box maven plugin which deploys/undeploy services to JBoss ESB application server, deploy and delete jBPM process (actually written on jPDL)?

    DB:3.29:Maven Plugin For Jboss Esb And Jbpm xf


    Thanks,it is also interesting what is sar-exploded and what are differences between sar and sar-exploded?I'm about this artifacthttp://mojo.codehaus.org/jboss-packaging-maven-plugin/sar-exploded-mojo.html

  • RELEVANCY SCORE 3.28

    DB:3.28:Newbie Esb Question - Object Returned From Web Service xf



    I am new to the JBoss ESB but can quickly see the power of this infrastructure. I have worked through several of the Quickstarts but I guess it's still not obvious to me. I have a simple web service and can invoke it via the ESB using the ServiceInvoker() from the client. My ESB config uses the SOAPClient to make the service request.

    The response to the client is a String containing the SOAP response. Instead I would like to get back the Object associated with the response - for example unmarshall the XML to the Java Object. Is there some other process I should be using in my action? Transformations?

    DB:3.28:Newbie Esb Question - Object Returned From Web Service xf


    I am new to the JBoss ESB but can quickly see the power of this infrastructure. I have worked through several of the Quickstarts but I guess it's still not obvious to me. I have a simple web service and can invoke it via the ESB using the ServiceInvoker() from the client. My ESB config uses the SOAPClient to make the service request.

    The response to the client is a String containing the SOAP response. Instead I would like to get back the Object associated with the response - for example unmarshall the XML to the Java Object. Is there some other process I should be using in my action? Transformations?

  • RELEVANCY SCORE 3.28

    DB:3.28:Jboss Esb Support For Clustering cm



    Does JBoss ESB suport clustering ?? I can't find any documentation about how to configure it!

    DB:3.28:Jboss Esb Support For Clustering cm


    "kurt.stam@jboss.com" wrote:Right now we are working on enabling loadbalancing/failover of service instances listenening to *different* buses. So you can play thicks with load balancing over different ftp servers, or different jms queus or even different jms providers. The latter should be on the trunk in the next week or so, examples and docs will follow after that.And once it's in, you've promised to do a blog entry around it, right :-)?

  • RELEVANCY SCORE 3.26

    DB:3.26:Jboss Esb Helloworld Quickstart Sample Issue 9z



    Hello All,

    I am fairly new to JBOSS And JBOSS-ESB.

    I downloaded and deployed JBOSS-AS and JBOSS-ESB seperately as well as JBOSS-ESB-SERVER, Both ways I am unable to run the 1st QuikStart Hello-World sample (I am using Windows-XP).

    When I use JBOSS-ESB-SERVER (Version-4.9)

    ===================================

    When running "ant deploy", following is the error thrown in the Server Console; So, I am unable to move to "ant runtest".

    17:23:48,765 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8

    080

    17:23:48,796 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009

    17:23:48,859 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos

    s_4_2_3_GA date=200807181417)] Started in 2m:28s:672ms

    17:26:34,125 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_gw]

    stopped

    17:26:34,125 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_esb

    ] stopped

    17:26:34,218 INFO [JBoss4ESBDeployer] create esb service, Quickstart_helloworld

    .esb

    17:26:34,234 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_esb

    ] started, fullSize=200000, pageSize=2000, downCacheSize=2000

    17:26:34,234 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_gw]

    started, fullSize=200000, pageSize=2000, downCacheSize=2000

    17:26:34,250 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

    --- MBeans waiting for other MBeans ---

    ObjectName: jboss.esb:service=JuddiRMI

    State: FAILED

    Reason: java.lang.ExceptionInInitializerError

    I Depend On:

    jboss.esb:service=JUDDIDatabaseInitializer

    jboss.esb:service=PropertyService

    Depends On Me:

    jboss.esb:service=JuddiClient

    --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---

    ObjectName: jboss.esb:service=JuddiRMI

    State: FAILED

    Reason: java.lang.ExceptionInInitializerError

    I Depend On:

    jboss.esb:service=JUDDIDatabaseInitializer

    jboss.esb:service=PropertyService

    Depends On Me:

    jboss.esb:service=JuddiClient

    When running JBOSS-AS (Version 6.0.0, Esb-Version - JBOSS-ESB-4.9)

    ======================================================

    I am able successfully deplot the service using "ant deploy", but when running "ant runtest" on the simple HelooWorld is fails with the following Errors on the Windows Console -

    compile:

    [javac] C:\JBoss-ESB\jbossesb-4.9\samples\quickstarts\conf\base-build.xml:43

    5: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=la

    st; set to false for repeatable builds

    [javac] C:\JBoss-ESB\jbossesb-4.9\samples\quickstarts\conf\base-build.xml:44

    0: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=la

    st; set to false for repeatable builds

    runtest:

    [echo] Runs Test JMS Sender

    [java] log4j:ERROR Could not instantiate class [org.jboss.logging.util.Only

    OnceErrorHandler].

    [java] java.lang.ClassNotFoundException: org.jboss.logging.util.OnlyOnceErr

    orHandler

    [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:202)

    [java] at java.security.AccessController.doPrivileged(Native Method)

    [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

    [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:307)

    I feel there are some serious config issues, but I am fairly new to ESB and JBOSS config, Can some body provide expert comments?

    Thanks.

    DB:3.26:Jboss Esb Helloworld Quickstart Sample Issue 9z


    jass,

    I am also quite new to JBOSS ESB got exactly the same error message already during startup of JBOSS ESB (and also when deploying helloworld with ant).

    solution in my case was rather simple: i had a blank in my JBOSS dir name ("../JBOSS ESB/..."). ;-)

    after removing the blank everything worked fine.

    dunno if this is any help for u...

    br,

    matthias

  • RELEVANCY SCORE 3.26

    DB:3.26:Using A Ftp Provider For A Single Esb Service cf



    Hi,

    I was trying to work on creating an esb service definition which is used by a jBPM process definition. One of the esb services in the jbpm process definition needs to read from a file on a well known FTP folder location. I am able to model this using ideas from the quick start bpm orch 2 example. However, the esb service jbpm node which has a configured FTP listener which uses the FTP channel from the FTP provider configuration does not leave this node even after reading the file from the FTP location. i.e., I need to trigger a node-leave event which for some reason doesnt happen and the process instance seems to be stuck, programmatically. I have configured the "starter service" and the "signal service" as per the bpm orch 2 and the bpm orch 3 sample quickstarts. Can someone please help me on this ?

    My env :

    OS : Windows 7

    JBoss ESB : 4.5.0 GA (JBAS 4.2.3)

    jBPM 3

    TIA.

    DB:3.26:Using A Ftp Provider For A Single Esb Service cf


    Ok. This seems to be fixed now. I was missing the MEP "One-Way" for the esb service actions. This way, the bpm node configured as an esb service with this setting will wait for the callback to be asynchronously sent to the bpm engine using the ServiceInvoker. Let me know if any further details are required w.r.t. how-to on this.

  • RELEVANCY SCORE 3.26

    DB:3.26:Running Out Of Memory With Simple_Cbr 7c



    I'm trying to run the example simple_cbr, but I'm getting this error:.....jbossesb/samples/quickstarts/simple_cbr/build.xml:15: java.lang.OutOfMemoryError: unable to create new native threadTotal time: 1 minute 4 secondsjava.lang.OutOfMemoryError: unable to create new native threadHow much memory is needed ? I have 1GB.I already stripped down JBossAS and JBoss ESB to a minimal configuration without all the HTTP stuff:1. contract.war2. http-invoker.sar3. jboss-web.deployer4. jbossws.sar5. jbpm.esb/jbpm-console.war6. jms/jbossmq-httpil.sar7. jmx-console.war8. management/console-mgr.sar9. soap.esb10. soapui-client.sarNow it works... but after a few times, I'm getting the error again. And all the system fails with:/usr/bin/lesspipe: fork: Resource temporarily unavailable-bash: fork: Resource temporarily unavailableThanks in advance,Eric

    DB:3.26:Running Out Of Memory With Simple_Cbr 7c


    I FOUND ITTTTT !!!!!!!!!!!!!!!!!!!!!!!!!I had restrictions in /etc/security/limits.conf.Well, at least, now I know how to reduce ESB at a minimal configuration.Thanks,Eric

  • RELEVANCY SCORE 3.26

    DB:3.26:Quickstarts ss



    I have committed the first phase of the reworked quickstarts, the changes involved are as follows.Each quickstart now contains *both* jbm and jbmq definitions. The appropriate definition will be automatically included in the .esb archive or deployed separately (via deploy-jms-dests) if running standalone. They also contain an appropriate deployment.xml to correctly force the deployment/undeployment order. All quickstart JMS MBeans are now prefixed with jboss.esb.quickstart.destination.It is no longer necessary to specify the lib directory, this is calculated automatically for jbossesb-server, build/jbossesb and source hierarchies.Building/deploying a quickstart from within the jbossesb-server hierarchy will only target the jbossesb-server. There is no need to specify the server home nor the profile being used due to an outstanding configuration issue.Building/deploying a quickstart from within the build/jbossesb or source hierarchy can target jboss-4.0.5, jboss-4.0.5-ejb3, jboss-4.2.0 and jboss-server.It is no longer necessary to specify the lib directory when installing the ESB into an app server. This is automatically calculated for source and build/jbossesb hierarchies.The following combinations were tested- jbossesb-server deploying into jbosseb-server- jbossesb-server running standalone against jbossesb-server- jbossesb deploying into jbossesb-server- jbossesb deploying into jboss-4.0.5 (or jboss-4.0.5-ejb3)- jbossesb deploying into jboss-4.2.0- jbossesb running standalone against jbossesb-server- jbossesb running standalone against jboss-4.0.5- jbossesb running standalone against jboss-4.2.0- source deploying into jbossesb-server- source deploying into jboss-4.0.5 (and jboss-4.0.5-ejb3)- source deploying into jboss-4.2.0- source running standalone against jbossesb-server- source running standalone against jboss-4.0.5- source running standalone against jboss-4.2.0The following quickstarts were tested- helloworld (all combinations)- helloworld_action (all combinations)- helloworld_file_action (all combinations)- helloworld_db_registration (all combinations)- helloworld_sql_action (all combinations)- more_action (all combinations)- transform_CSV2XML (all combinations)- transform_EDI2XML_Groovy_XSLT (all combinations)- transform_XML2POJO (all combinations)- transform_XML2XML_date_manipulation (all combinations)- transform_XML2XML_simple (all combinations)- simple_cbr (all combinations)- fun_cbr (all combinations)- scripting_groovy (all combinations)- bpm_orchestration1 (all deployable combinations)- jbpm_simple1 (all deployable combinations)- static_router (all combinations)- helloworld_ftp_action (all combinations)- aggregator (all standalone combinations)- business_service (jbossesb and source deploying to 4.0.5-ejb3 and 4.2.0)The CBR tests were executed using revision 12265 of services/jbrules. The current HEAD version had conflicts due to a *third* version of antlr being includedThe use of scoped JBoss Messaging in an app server environment is not supported at this time.

    DB:3.26:Quickstarts ss


    Well for each quickstart you could attach all your updates in one attachment to your jira entry. That would be really helpful. Thanks :) --Kurt

  • RELEVANCY SCORE 3.24

    DB:3.24:What Version Of As In Jboss Esb Server fd


    "Getting Started With JBoss ESB" for 4.7 says that JBoss ESB Server "is a stripped down version of the JBoss application server". What version of JBoss AS does this correspond do?

    DB:3.24:What Version Of As In Jboss Esb Server fd

    I guess that I was looking so hard, I couldn't see what was right in front of me!

  • RELEVANCY SCORE 3.24

    DB:3.24:Compare Between Open Source Esb Products (Jboss Esb, Openesb, Mule Esb And Apache Service Mix)) kj



    Hallo,

    i want to compare the following open source esb products: Mule esb, Sun open esb , JBoss esb and Apache ServiceMix. Hat someone any idea about a progrmming example or about a roadmap to efficiency compare them und test their performance?

    thanks in advance

    Younes

    DB:3.24:Compare Between Open Source Esb Products (Jboss Esb, Openesb, Mule Esb And Apache Service Mix)) kj


    Hello Younes,

    If it's still relevant, then here's the right article to start with [1]. There is a section inside that summarizes (though in short) open source ESB products.

    I believe you might find it intersting.

    1: http://media.techtarget.com/searchSOA/downloads/OpenSourceCH2.pdf

    Cheers,

    Andrzej

  • RELEVANCY SCORE 3.23

    DB:3.23:Deploy Fuse Esb 4.4.1 On Jboss 7.0 kd



    Hi,

    I need to deploy fuse esb on Jboss 7.0.

    How can we deploy the fuse esb on jboss server?

    Thanks,

    Dharmendra

  • RELEVANCY SCORE 3.23

    DB:3.23:+ Problem With The Helloworld Quickstart + x7



    Hello Kurt,I try to use my new brand jbossesb installation with the Hello World QuickStart but this doesn't work fine. This is the trace after the start of the "ant run" task. I see that this is a connection problem.can you tell me what I can do to solve this problem.
    [echo] Basic JMS Gateway and Listener
    [java] 21:20:30,984 INFO [main][Launcher] args passed into Launcher: 3
    [java] 21:20:31,000 INFO [main][Launcher] arg[0]=0
    [java] 21:20:31,000 INFO [main][Launcher] arg[1]=C:\dev\workspace-2\jboss-esb\product\samples\quickstarts\helloworld_embedded_reg/../helloworld/esb-config.xml
    [java] 21:20:31,000 INFO [main][Launcher] arg[2]=C:\dev\workspace-2\jboss-esb\product\samples\quickstarts\helloworld_embedded_reg/../helloworld/esb- config-gateway.xml
    [java] 21:20:31,125 INFO [main][HsqldbUtil] creating db from this script: build/hsqldb
    [java] [Server@a97b0b]: [Thread[main,5,main]]: checkRunning(false) entered
    [java] [Server@a97b0b]: [Thread[main,5,main]]: checkRunning(false) exited
    [java] [Server@a97b0b]: Startup sequence initiated from main() method
    [java] [Server@a97b0b]: Loaded properties from [C:\dev\workspace-2\jboss-esb\product\samples\quickstarts\helloworld_embedded_reg\server.properties]
    [java] [Server@a97b0b]: Initiating startup sequence...
    [java] [Server@a97b0b]: [Thread[HSQLDB Server @a97b0b,5,main]]: run()/openServerSocket():
    [java] java.net.BindException: Address already in use: JVM_Bind
    [java] [Server@a97b0b]: Initiating shutdown sequence...
    [java] at java.net.PlainSocketImpl.socketBind(Native Method)
    [java] [Server@a97b0b]: Shutdown sequence completed in 0 ms.
    [java] at java.net.PlainSocketImpl.bind (PlainSocketImpl.java:359)
    [java] at java.net.ServerSocket.bind(ServerSocket.java:319)
    [java] at java.net.ServerSocket.init(ServerSocket.java:185)
    [java] [Server@a97b0b]: 2006-12-05 21:20:31.312 SHUTDOWN : System.exit() is called next
    [java] at java.net.ServerSocket.init(ServerSocket.java:97)
    [java] at org.hsqldb.HsqlSocketFactory.createServerSocket(Unknown Source)
    [java] at org.hsqldb.Server.openServerSocket (Unknown Source)
    [java] at org.hsqldb.Server.run(Unknown Source)
    [java] at org.hsqldb.Server.access$000(Unknown Source)
    [java] at org.hsqldb.Server$ServerThread.run(Unknown Source)

    DB:3.23:+ Problem With The Helloworld Quickstart + x7


    Maybe runing the examples with Mysql DB is better and esasier.

  • RELEVANCY SCORE 3.23

    DB:3.23:Jboss Esb Installation To Jboss As 6.1.0.Final 17



    I am new to JBoss ESB and I was wondering, if anyone has successfully installed JBoss ESB with JBoss AS 6.1?

    Thanks.

    DB:3.23:Jboss Esb Installation To Jboss As 6.1.0.Final 17


    Actually, deploying the ESB onto JBoss AS 6.1 is pretty straightforward. I am currently interested on deploying and configuring PicketLink 2.0 on JBoss AS 6.1 for ADFS authentication.

    There are some excellent instructions for JBoss AS 7.1; but, can't seem to find instructions tailored for 6.1.

    (e.g. https://community.jboss.org/wiki/HowToConfigurePicketLink202WithJBossAS711?_sscc=t).

    Does anyone have a reference on "How to configure PicketLink 2.0.2 with JBoss AS 6.1"?

  • RELEVANCY SCORE 3.23

    DB:3.23:Is Jboss Esb Jbi Compliant? cz



    Hi, I can't find if JBoss ESB is or not JBI compliant... thanks

    DB:3.23:Is Jboss Esb Jbi Compliant? cz


    tal.beno,I would love to hear about the Binding Components and Service Engines that you would like to build/use and therefore need a JBI-compliant container. Feel free to contact me via these forums (or via email) to discuss your BC SE needs.Thank you,Burr

  • RELEVANCY SCORE 3.23

    DB:3.23:Does Jboss Esb Supports Jboss As 7.1.X ss



    Hi,Does JBoss ESB Supports JBoss AS 7.1.x?

    Thanks,

    Velmurugan Rajendran

    DB:3.23:Does Jboss Esb Supports Jboss As 7.1.X ss


    No. JBoss ESB can be installed on JBoss AS 4.2.3.GA, 5.1.0.GA, or 6.1.0.Final, but there's no support for JBoss AS 7. If you're looking for a similar project with AS 7 support, you should investigate SwitchYard (http://www.jboss.org/switchyard).

    Here's a prior thread with more information around this :

    https://community.jboss.org/thread/172256

  • RELEVANCY SCORE 3.23

    DB:3.23:Problem Facing While Implementing Example Helloworld_Ftp_Act kj



    Hi,While implementing example jbossesb-4.2MR3\samples\quickstarts\helloworld_ftp_action I am a facing problem.I had configured a connection to local FTP server from JBoss ESB to read message from FTP server location, but ended up with following exception: [java] Reading config from E:\jbossesb-4.2MR3\samples\quickstarts\helloworld_ftp_action\jboss-esb.xml [java] 16:19:41,824 ERROR [Thread-2][EdtFtpImpl] Caught FTPException. [java] com.enterprisedt.net.ftp.FTPException: File renamed [java] at com.enterprisedt.net.ftp.FTPControlSocket.validateReply(FTPControlSocket.java:923) [java] at com.enterprisedt.net.ftp.FTPClient.rename(FTPClient.java:2494) [java] at org.jboss.internal.soa.esb.util.EdtFtpImpl.remoteRename(EdtFtpImpl.java:489) [java] at org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener.renameFile(RemoteGatewayListener.java:208) [java] at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.doRun(AbstractFileGateway.java:141) [java] at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) [java] at java.lang.Thread.run(Thread.java:595) [java] 16:19:41,887 ERROR [Thread-2][AbstractFileGateway] Problems renaming file HWFtp-11-Oct-07-15-41-00.dat to HWFtp-11-Oct-07-15-41-00.dat.esbInProcessIn readme.txt file, it is specified that ?this problem will come when we don?t have write permission on remote FTP server location?.But I had given full permissions on remote FTP server location. Did I missed any other configuration settings?I am usingFTP server: Xlight FTP serverJBoss ESB: jbossesb-4.2MR3JBoss AS: jboss-4.0.5.GAPlease pour some inputs.Thanks,-Vidya

    DB:3.23:Problem Facing While Implementing Example Helloworld_Ftp_Act kj


    Hi,Jira ticket #JBESB-303 help me in resolving the problem.Ticket says it is the problem with some type of FTP servers. I had installed trial version WinFtp Server and now it is working fine. Previously I was tried Xlight FTP server and Golden FTP server. WinFtp Server resolved my problem.Burrsutter, Kevin,Thanks a lot for given support.Thanks,-Vidya

  • RELEVANCY SCORE 3.22

    DB:3.22:Problem In Executing Bpm_Orchestration2 Sample px



    I am using jboss-soa-p.4.2.0 and am currently working on jbossesb and jbpm integration.I am executing the bpm_orchestration2 sample in .esb archive mode using the steps given in readme.My ant deploy works fine and there is no error in server log.But when i do ant deployProcess i get the following error and hence i dont find 'Process Definition Deployed:' to appear on the console.
    C:\jboss-soa-p.4.2.0\jboss-as\samples\quickstarts\bpm_orchestration2ant deployP
    rocess
    Buildfile: build.xml

    check-jbossesb-dist:

    qslib-dependencies:

    non-qslib-dependencies:

    jbossesb-quickstart-override:

    jbossesb-source-dependencies:

    jbossesb-server-dependencies:
    [echo] Defaulting to profile: production

    jbossesb-dependencies:

    messaging-config:

    messaging-dependencies:

    jbossmq-dependencies:

    quickstart-specific-dependencies:

    classpath-dependencies:

    quickstart-specific-checks:

    dependencies:

    deployProcess:
    [echo] Deploy the process definition
    [deployToServer] An unexpected exception happened while testing the server (http
    ://localhost:8080/jbpm-console/upload) connection.

    BUILD SUCCESSFUL
    Total time: 2 seconds

    DB:3.22:Problem In Executing Bpm_Orchestration2 Sample px


    Can you check your quickstarts/conf/quickstarts.properties file and make sure that you have uncommented the username and password for the jbpm console:
    # jBPM console security credentials (if org.jboss.esb.server.config=production)
    #jbpm.console.username=admin
    #jbpm.console.password=admin

  • RELEVANCY SCORE 3.21

    DB:3.21:Comments On Overlord-Cdl-1.0-M1 Trailblazer Example pf



    The readme describes how to deploy and run the application, but there is no discussion that I could find on the role of CDL in the trailblazer. While there is a TrailBlazer.cdm in the models folder, and by inspection, one can tell that it is included in the trailblazer.esb, it is not clear what role it is playing.Second. I would like to see the examples not configure all of the services in a single jboss-esb.xml file and deploy via a single esb archive. While this has been the practice in the past with the quickstarts, I believe it is a bad practice. If a benefit of a service-based approach is that each service can be independently deployed, this benefit is negated when all services are configured in the same xml file.Thanks,Jeff

    DB:3.21:Comments On Overlord-Cdl-1.0-M1 Trailblazer Example pf


    A few suggestions on how to improve the documentation:1) Have the readme refer to the docs/samplesguide/SamplesGuide. While much of the information is redundant, the SamplesGuides has the information on the ChoreographyMonitor and the error-client.2) In the SamplesGuide.pdf, the code snippet from LoanBroker.java is unreadable.3) Under 10 2 It says to run the commands from step 6 on. Is that really necessary?4) Add more information on the role of the LoanBroker.java class, and how it's choice of if (score = 4) { //step 3a - send to Bank - async System.out.println("sending to first Bank..."); sendToBank(bank1Invoker, customer, "b1");Implements the Choreography conditional expression: cdl:getVariable('creditCheckResult','','//@score') = 45) It would be nice to have an architectural discussion here about how this choreography is being monitored. (perhaps this is described in another document I have yet to read).Thanks,Jeff

  • RELEVANCY SCORE 3.20

    DB:3.20:Smookstransformer Problem In The Quickstarts Samples: Fun_Cbr c7



    Hi, I am trying to run quickstart example of jbossesb4.7: fun_cbr.

    However, after I add the following code according to the introduction of readme.txt in jboss-esb.xml:

    action name="transform" class="org.jboss.soa.esb.actions.converters.SmooksTransformer"

    property name="resource-config" value="/smooks-res.xml" /

    /action

    action name="convertPOJO2Message" class="org.jboss.soa.esb.dvdstore.DVDStoreAction" /

    !-- this will send everything to the console --

    action name="dump" class="org.jboss.soa.esb.actions.SystemPrintln"

    property name="printfull" value="true"/

    /action

    It does't work, esb server gives warning:

    WARN [ActionProcessingPipeline] No fault address defined for fault message!

    To: JMSEpr [ PortReference wsa:Address jms:127.0.0.1:1099#queue/quickstart_Fun_CBR_ToGreenTransformer/,

    wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/,

    wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/,

    wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/,

    wsa:ReferenceProperties jbossesb:destination-type : queue/,

    wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_Fun_CBR_ToGreenTransformer/,

    wsa:ReferenceProperties jbossesb:specification-version : 1.1/,

    wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/,

    wsa:ReferenceProperties jbossesb:persistent : true/,

    wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/,

    wsa:ReferenceProperties jbossesb:transacted : false/,

    wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/ ]

    MessageID: 9ce43be2-6746-43e9-9754-9a793299e890

    RelatesTo: jms:correlationID#9ce43be2-6746-43e9-9754-9a793299e890

    thanks

    DB:3.20:Smookstransformer Problem In The Quickstarts Samples: Fun_Cbr c7


    Hi, I am trying to run quickstart example of jbossesb4.7: fun_cbr.

    However, after I add the following code according to the introduction of readme.txt in jboss-esb.xml:

    action name="transform" class="org.jboss.soa.esb.actions.converters.SmooksTransformer"

    property name="resource-config" value="/smooks-res.xml" /

    /action

    action name="convertPOJO2Message" class="org.jboss.soa.esb.dvdstore.DVDStoreAction" /

    !-- this will send everything to the console --

    action name="dump" class="org.jboss.soa.esb.actions.SystemPrintln"

    property name="printfull" value="true"/

    /action

    It does't work, esb server gives warning:

    WARN [ActionProcessingPipeline] No fault address defined for fault message!

    To: JMSEpr [ PortReference wsa:Address jms:127.0.0.1:1099#queue/quickstart_Fun_CBR_ToGreenTransformer/,

    wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/,

    wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/,

    wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/,

    wsa:ReferenceProperties jbossesb:destination-type : queue/,

    wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_Fun_CBR_ToGreenTransformer/,

    wsa:ReferenceProperties jbossesb:specification-version : 1.1/,

    wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/,

    wsa:ReferenceProperties jbossesb:persistent : true/,

    wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/,

    wsa:ReferenceProperties jbossesb:transacted : false/,

    wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/ ]

    MessageID: 9ce43be2-6746-43e9-9754-9a793299e890

    RelatesTo: jms:correlationID#9ce43be2-6746-43e9-9754-9a793299e890

    thanks

  • RELEVANCY SCORE 3.20

    DB:3.20:Os Quickstarts Da Comunidade Jboss: Como Rodar c3



    Ol pessoal,

    Postei em meu blog como rodar um quickstart bem simples, o "helloworld". Em breve(hoje a noite) postarei um vdeo para demonstrar o uso desses quickstarts.

    Segue o link!!

    http://aprendendo-javaee.blogspot.com.br/2014/01/aprendendo-java-ee-rapidamente-com-os.html

  • RELEVANCY SCORE 3.19

    DB:3.19:Spring Integration Checked In. Seeking Developer Review xk



    I've checked in code for these 2 jira tasks:Spring integration quickstarts: http://jira.jboss.com/jira/browse/JBESB-367For those too busy to read the Jira tickets, here's a quick rundown of the Spring quickstarts:1. product/samples/quickstarts/spring_helloworld - simple loading/invoking of a spring bean2. product/samples/quickstarts/spring_aop - simple SpringAOP example3. product/samples/quickstarts/spring_jpetstore - more complicated Spring example that uses Spring managed DB connection pool/datasource, SpringTX, SpringAOP and iBatis for DB access.Java class located at: product/core/listeners/src/org/jboss/soa/esb/actions/AbstractSpringAction.java that provides decent way to use Spring in the ESB:http://jira.jboss.com/jira/browse/JBESB-592There are unit tests for this code in: product/core/listeners/tests/src/org/jboss/soa/esb/actions/springIf you're interested in Spring integration in the ESB, feel free to review and provide feedback.James

    DB:3.19:Spring Integration Checked In. Seeking Developer Review xk


    I've checked in code for these 2 jira tasks:Spring integration quickstarts: http://jira.jboss.com/jira/browse/JBESB-367For those too busy to read the Jira tickets, here's a quick rundown of the Spring quickstarts:1. product/samples/quickstarts/spring_helloworld - simple loading/invoking of a spring bean2. product/samples/quickstarts/spring_aop - simple SpringAOP example3. product/samples/quickstarts/spring_jpetstore - more complicated Spring example that uses Spring managed DB connection pool/datasource, SpringTX, SpringAOP and iBatis for DB access.Java class located at: product/core/listeners/src/org/jboss/soa/esb/actions/AbstractSpringAction.java that provides decent way to use Spring in the ESB:http://jira.jboss.com/jira/browse/JBESB-592There are unit tests for this code in: product/core/listeners/tests/src/org/jboss/soa/esb/actions/springIf you're interested in Spring integration in the ESB, feel free to review and provide feedback.James

  • RELEVANCY SCORE 3.19

    DB:3.19:Does Jboss Esb Violate The Jee 5 Specification? f1


    Does JBoss ESB violate the JEE 5 Specification?

    DB:3.19:Does Jboss Esb Violate The Jee 5 Specification? f1


    Hiya Peer.

    I have already created an issue to revisit the documentation covering the integration of WSMQ, part of this task will also look at whether we can use the JCA in specific circumstances.

    Kev

  • RELEVANCY SCORE 3.18

    DB:3.18:Esb And Jboss Enterprise 83



    Hi,Is it possible to get JBoss ESB under JBoss Enterprise license? What is the supported version? If no, are there any plans?Thanks.

    DB:3.18:Esb And Jboss Enterprise 83


    There will be a supported product in the future. However, we are working with some organizations who are interested in having some support today. Please contact me directly if you feel that your organization would like to engage in a partnership and/or "beta" program with JBoss/Red Hat.Thanks,Burr

  • RELEVANCY SCORE 3.17

    DB:3.17:Jboss Esb Queue Subscribing Issue x8



    Guys,

    We are using Jboss ESB for Message routing and File routing. JBoss ESB should subscribe the Queue from JBoss Messaging server(Jboss AS) and route the messages to file. Everything is working fine if JBoss Messaging Server starts before JBoss Esb. But if JBoss ESB started later than JBoss Messaging,it is not subscribing and Jboss ESB is not be able to receive any messages from JBoss Messaging Server.

    Documentation says that sessionSleep will help to solve this kind of issues But does not work.

    property name="org.jboss.soa.esb.jms.sessionSleep" value="30"/

    If anybody has an idea, please share with us,

    Thanks in advance

    Raj.

    DB:3.17:Jboss Esb Queue Subscribing Issue x8


    Hi Tom,

    Messaging server and ESB are running in two different Servers.

    Thanks,

    Raj.

  • RELEVANCY SCORE 3.17

    DB:3.17:Incompletely Deployed Packages 1c



    Hi,New to JBoss ESB and need some help. Running ESB server 4.2.1 GA tested against some of the quickstarts which execute correctly.At this point I am trying to deploy the console app under {esb-root-dir}/tools - I manage to successfully build the esb archive:------------------------------------------------------------------------------------Buildfile: build.xmlbuild: [delete] Deleting: /Applications/jbossesb-server-4.2.1GA/tools/console/jboss-esb-console.ear [echo] ----------------------------------------------------------- [echo] | | [echo] | J B O S S E S B A D M I N I S T R A T I O N | [echo] | C O N S O L E C O N F I G | [echo] | | [echo] ----------------------------------------------------------- [echo] This script will help you configure your JBoss ESB Administration Console Application. [echo] You can reconfigure at any time by re-running this script. [input] Press enter to start... [input] Enter the target database type:(hsqldb,postgres)hsqldb [echo] JBoss 4.0.5.GA and JBoss 4.2.0.GA use differing implementations of JSF. If you are deploying to JBoss 4.0.5.GA, please select myfaces as JSF provider. If you are using JBoss 4.2.0.GA or higher, select jbossfaces. [input] Enter the JSF provider:(myfaces,jbossfaces)jbossfaces [delete] Deleting: /Applications/jbossesb-server-4.2.1GA/tools/console/console/distro/hsqldb/jboss-esb-console.distro.propertiescapture-config:jsf-copy: [copy] Copying 1 file to /Applications/jbossesb-server-4.2.1GA/tools/console/console/jboss-esb-console.war/WEB-INFjsf-excludes:filter-files: [copy] Copying 1 file to /Applications/jbossesb-server-4.2.1GA/tools/console/console/jboss-esb-console.jar/META-INF [copy] Copying 1 file to /Applications/jbossesb-server-4.2.1GA/tools/console/console/jboss-esb-console.ear/META-INFfilter-ds-file:archive: [mkdir] Created dir: /Applications/jbossesb-server-4.2.1GA/tools/console/temp [jar] Building jar: /Applications/jbossesb-server-4.2.1GA/tools/console/temp/jboss-esb-console.jar [jar] Building jar: /Applications/jbossesb-server-4.2.1GA/tools/console/temp/jboss-esb-console.war [jar] Building jar: /Applications/jbossesb-server-4.2.1GA/tools/console/jboss-esb-console.ear [delete] Deleting directory /Applications/jbossesb-server-4.2.1GA/tools/console/tempoutput-instructions: [echo] *********** 1. COPY the "jboss-esb-console.ear" file to your JBoss Application Server "deploy" folder. [echo] *********** 2. Access the console through "http://localhost:8080/jboss-esb-console/" (replacing the host and port as appropriate).BUILD SUCCESSFULTotal time: 30 seconds------------------------------------------------------------------------------------I copy the esb archive to my deploy directory but in my server logs I get the following error when it tries to deploy the archive into the runtime env:15:47:56,946 ERROR [URLDeploymentScanner] Incomplete Deployment listing:--- Packages waiting for a deployer ---org.jboss.deployment.DeploymentInfo@c5a0054c { url=file:/Applications/jbossesb-server-4.2.1GA/server/default/deploy/jboss-esb-console.ear } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/Applications/jbossesb-server-4.2.1GA/server/default/deploy/jboss-esb-console.ear altDD: null lastDeployed: 1203520274645 lastModified: 1203520274000 mbeans:--- Incompletely deployed packages ---org.jboss.deployment.DeploymentInfo@c5a0054c { url=file:/Applications/jbossesb-server-4.2.1GA/server/default/deploy/jboss-esb-console.ear } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/Applications/jbossesb-server-4.2.1GA/server/default/deploy/jboss-esb-console.ear altDD: null lastDeployed: 1203520274645 lastModified: 1203520274000 mbeans:In the build I stipulate hsqldb - presume the default hsqldb-ds.xml in the deploy dir will be used and therefore a missing db connection prop file is not the cause of this problem.Appreciate any assistance.

    DB:3.17:Incompletely Deployed Packages 1c


    In the pre-JBoss DNA world, what's the consensus on what that web app would look like?Would it be something like AquaLogic where you can choose an endpoint and a gateway and then drag pre-configured actions between them?Or would it be more targetted/useful to have an app that combined a rules/transformation registry (with CRUD and versioning capabilities) on one set of pages with a second page that contained with a treeview of the registered services/EPRs and the ability to map them to rules/transformations from the repository?

  • RELEVANCY SCORE 3.17

    DB:3.17:Jboss 5.0.1 And Esb 4.9 kx



    Does anyone know if JBoss 5.0.1 works with any of the current ESB releases?

    Thaks,

    Steve

    DB:3.17:Jboss 5.0.1 And Esb 4.9 kx


    Just to double check - your agency has standardized on JBoss AS 5.0.1? Not EAP 5.0.1 or SOA-P 5.0.1?

    I finally got a few minutes to try the AS 5.0.1 scenario. There are errors on install - the binding service is configured differently from 5.1.0.GA, which you would have to sort out. I don't know what possible errors lie beyond that.

  • RELEVANCY SCORE 3.17

    DB:3.17:Handling Service Response In A Standalone Jms Client 33



    I have a simple setup similar to the helloworld sample from the quickstarts. I am using a simple, standalone JMS client to dispatch a text message to a JMS gateway on which a ESB service is listening.The JMS client blocks listening for service response on a reply queue (request queue name_reply).According to the "Programmers Guide", and correct me if I am wrong, once the last action finishes processing the message, the action pipeline automatically places the message on the queue: (request queue name_reply), given that the actions mep attribute is set to RequestResponse in jboss-esb.xml.If that is true, it is not working in my case. I am trying to figure out an optimum setup for such a scenario and so far, I could only get it to work by adding a JMSRouter action at the end of the pipeline.Your help is appreciated. Thanks.

    DB:3.17:Handling Service Response In A Standalone Jms Client 33


    I want use the JMS approch too, but without the JMSRouter trick, because the service is used through the native ESB bus too.Any advice?BR / DGOM

  • RELEVANCY SCORE 3.16

    DB:3.16:Ws Producer Example 3j



    Hello,I was trying to deploy the webservice_producer example from the quickstarts, but ran into

    ObjectName: jboss.esb:deployment=Quickstart_webservice_producer.esb
    State: FAILED
    Reason: java.lang.NoClassDefFoundError: org/jboss/wsf/spi/invocation/BasicInvocationContext
    I Depend On:
    ...

    DB:3.16:Ws Producer Example 3j


    Great find troyer, thanks a lot! This would be the end of the producer problem.JBoss-guys, could you include the JBossRemoting 2.2.2SP2 note in the readme file for the next version?Thanks to all who helped out with this.All the best.

  • RELEVANCY SCORE 3.16

    DB:3.16:Esb Vs. As/Esb j9



    Hello,

    What is the difference between installing just JBoss ESB vs. installing JBoss ESB onto a system that already has AS installed.

    Does the ESB server run under AS? Does AS assume the responsiblities of the ESB Server?

    Any insight into the high-level architectural differences between these two configurations would be appreciated.

    Thanks

    DB:3.16:Esb Vs. As/Esb j9


    ESB Server is a slimmed down JBoss AS based on 4.2.3.GA that does not include EJB3 support. It starts up a lot quicker than JBoss AS. If you want to use AS 5 features or EJB3 or deploy in an EAR, use the AS. If you're doing development locally, you might think about using the ESB server if you don't need those features.

  • RELEVANCY SCORE 3.16

    DB:3.16:How To Use Jboss Serialization In Jboss Esb s9



    Hi Question from subject : how to use / replace standard java serialization to Jboss serialization in Jboss Esb? Antony

  • RELEVANCY SCORE 3.16

    DB:3.16:How To Configure Jboss Esb 4.2.2 With Oracle dd



    can anyone send me step by step how to install jboss ESB 4.2.2 with oracle10gI read alll docs but donot find how to configure oracle with jboss ESBthanxregardsprince

    DB:3.16:How To Configure Jboss Esb 4.2.2 With Oracle dd


    in this line I'm facing problem jboss:service=Hypersonic,database=juddiDBI wanna convert it to oracle so that I can use it with oracleDo you mean the in the file jbossesb.sar/juddi-ds.xml ? If that is the case, step two in the url that I posted describes that this file should have been updated and that should not be there.

  • RELEVANCY SCORE 3.16

    DB:3.16:What's The Difference Between Jboss Esb4.2, Esb4.3 And Esb4. j1



    if I want to develop a esb using JBoss ESB, how to choose the esb version, are there any differences between these esb versions?Thanks

    DB:3.16:What's The Difference Between Jboss Esb4.2, Esb4.3 And Esb4. j1


    This is not an appropriate question for the design forums. I will move this to the user forums.

  • RELEVANCY SCORE 3.16

    DB:3.16:Possible To Update 'Infinispan Quickstarts' To (At Least) 5.1.0.Cr1 d3



    Hi,

    I have recently upgraded as7 from 7.0.2 to 7.1.0.CR1, which introduced infinispan 5.1.CR1. Trying to start distributed cache against latest available quickstarts examples(specially 'jboss-as7-quickstart') has given me some trouble.

    The snippet from Controller.java, condition
    if (cache.getConfiguration().getCacheMode() != CacheMode.LOCAL) {

    DB:3.16:Possible To Update 'Infinispan Quickstarts' To (At Least) 5.1.0.Cr1 d3


    Just yesterday Pete posted a blog entry where he explained the new configuration, see: http://infinispan.blogspot.com/2012/01/configuration-changes-in-infinispan.html

  • RELEVANCY SCORE 3.16

    DB:3.16:Jboss Esb Plugin Eclipse Tool Problem p8



    I have installed the ESB plugin and I have JBoss AS and JBoss ESB up and running. I ran the ESB HelloWorld test and it seem to run fine. I am trying to get a new project installed and I am getting an error:It says that I have an invalid ESB Install location:I installed JBoss AS in the following location:C:\dev\applications\jboss-4.2.3.GAI installed JBoss ESB in the following location:C:\dev\applications\jbossesb-4.5.GA\Is this the correct location or is it referring to the location of where the ESBs have been deployed with in JBoss ASThank in advanceShannon

    DB:3.16:Jboss Esb Plugin Eclipse Tool Problem p8


    Can you post your deployment.properties and the ant command you ran to install JBoss ESB within the AS?

  • RELEVANCY SCORE 3.14

    DB:3.14:Jboss Esb In Jboss As 5.0 cm



    Dear All,There is an entry on the JIRA about supporting JBoss EBS 4.x on JBoss AS 5.0I would like to know if JBoss ESB 4.x can be deploy on JBoss AS 5.0.If no, would you please let me know when AS 5.0 is supported by the ESB?Bests,Soheil

    DB:3.14:Jboss Esb In Jboss As 5.0 cm


    Hi Soheil,
    2. What about the trunk, can I use it on 5.0 AS ?Not yet. I've not merged the changes required back to the main trunk yet. 3. Anybody's workspace on the SVN deployable on JBoss AS 5.0?Yes, but at the moment this requires patches to AS 5. We will hopefully have our required changes in an AS branch in the next days or so. I'll then post to the forums with information about how you can try this out. I'll update this thread at that time so that you are informed of it. Regards, /Daniel

  • RELEVANCY SCORE 3.12

    DB:3.12:Migrating To Jboss 5.0 And Esb 4.8 fd



    Hi All,

    What could be the main benefits of migrating the application from JBoss 4.2.3/ESB 4.4 to JBoss 5.0/ESB 4.8?

    Thanks.

    DB:3.12:Migrating To Jboss 5.0 And Esb 4.8 fd


    and to extend the question, which what particular combination of Jboss AS/ESB after version Jboss 4.2.3/ESB 4.4, respectively gives better performance and functionality?

  • RELEVANCY SCORE 3.12

    DB:3.12:How To Configure Jboss Esb Queues ? 3d


    I am very new to Jboss AS and HornetQ.
    Previously i am using Jboss AS 5.0.0 with Jboss ESB 4.9 so i get upgraded to Jboss 6.1.0.0 with Jboss ESB 4.11, now i need ton configuration IBM MQ to Jboss AS 6.1.0 final with Jboss ESB 4.11 And how to configure Jboss ESB project into Jboss AS 6.1.0 final server
    and previous i am using Jbpm-Queue-service.xml to configure Jboss ESB Queues gateway queues, but in latest version how to configure Jboss ESB Queues?
    Please help..

    DB:3.12:How To Configure Jboss Esb Queues ? 3d

    I am very new to Jboss AS and HornetQ.
    Previously i am using Jboss AS 5.0.0 with Jboss ESB 4.9 so i get upgraded to Jboss 6.1.0.0 with Jboss ESB 4.11, now i need ton configuration IBM MQ to Jboss AS 6.1.0 final with Jboss ESB 4.11 And how to configure Jboss ESB project into Jboss AS 6.1.0 final server
    and previous i am using Jbpm-Queue-service.xml to configure Jboss ESB Queues gateway queues, but in latest version how to configure Jboss ESB Queues?
    Please help..

  • RELEVANCY SCORE 3.10

    DB:3.10:Error On Line 46 Of Build.Xml In The Webservice_Producer Sam ks



    Hi people,Please, does anybody have already gotten this error when running 'ant runtest' for the sample webservice_producer?Please, take a look at the error:C:\jbossesb-4.2.1GA\samples\quickstarts\webservice_producerant runtestBuildfile: build.xmlcheck-jbossesb-dist:qslib-dependencies:non-qslib-dependencies:jbossesb-dependencies:jbossesb-server-dependencies:messaging-config:messaging-dependencies:jbossmq-dependencies:assert-ws-available: [echo] JBoss Webservice container found on target 'c:jboss-4.2.1.GA/server/default/deploy'.quickstart-specific-dependencies:dependencies:compile:runtest:check-jbossesb-dist:qslib-dependencies:non-qslib-dependencies:jbossesb-dependencies:jbossesb-server-dependencies:messaging-config:messaging-dependencies:jbossmq-dependencies:assert-ws-available: [echo] JBoss Webservice container found on target 'c:jboss-4.2.1.GA/server/default/deploy'.quickstart-specific-dependencies:dependencies:compile:saygoodbye_over_jms: [echo] Invoking a JBossWS Endpoint over JMS (via JBoss ESB).check-jbossesb-dist:qslib-dependencies:non-qslib-dependencies:jbossesb-dependencies:jbossesb-server-dependencies:messaging-config:messaging-dependencies:jbossmq-dependencies:assert-ws-available: [echo] JBoss Webservice container found on target 'c:jboss-4.2.1.GA/server/default/deploy'.quickstart-specific-dependencies:dependencies:compile:saygoodbye_over_http: [echo] Invoking a JBossWS Endpoint over HTTP (via JBoss ESB). [java] Calling JBoss Remoting Listener using locator URI: http://localhost:8765 [java] Exception in thread "main" org.jboss.remoting.CannotConnectException: Can not connect http client invoker. [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:332) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135) [java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) [java] at org.jboss.remoting.Client.invoke(Client.java:1550) [java] at org.jboss.remoting.Client.invoke(Client.java:530) [java] at org.jboss.remoting.Client.invoke(Client.java:518) [java] at org.jboss.soa.esb.samples.quickstart.webserviceproducer.test.SendMessage.sendMessageToJBRListener(SendMessage.java:72) [java] at org.jboss.soa.esb.samples.quickstart.webserviceproducer.test.SendMessage.main(SendMessage.java:114) [java] Caused by: java.net.ConnectException: Connection refused: connect [java] at java.net.PlainSocketImpl.socketConnect(Native Method) [java] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) [java] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) [java] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) [java] at java.net.Socket.connect(Socket.java:519) [java] at java.net.Socket.connect(Socket.java:469) [java] at sun.net.NetworkClient.doConnect(NetworkClient.java:157) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:382) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:494) [java] at sun.net.www.http.HttpClient.(HttpClient.java:231) [java] at sun.net.www.http.HttpClient.New(HttpClient.java:304) [java] at sun.net.www.http.HttpClient.New(HttpClient.java:316) [java] at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817) [java] at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769) [java] at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694) [java] at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:861) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:274) [java] ... 7 moreBUILD FAILEDC:\jbossesb-4.2.1GA\samples\quickstarts\webservice_producer\build.xml:32: The following error occurred while executing this line:C:\jbossesb-4.2.1GA\samples\quickstarts\webservice_producer\build.xml:46: Java returned: 1Total time: 16 secondsC:\jbossesb-4.2.1GA\samples\quickstarts\webservice_producerI ran 'ant deploy' before run the task above and the JBoss AS with JBossESB deployed in was running.Thanks in advance!Regards,Luiz

    DB:3.10:Error On Line 46 Of Build.Xml In The Webservice_Producer Sam ks


    Hi Luiz,the webservice_producer quickstart requires webservice support being installing into the applicationserver. If you are using JBoss AS 4.2.0.GA the take a look at the "Configuring Webservice Integration" section of theJBossESB Adminsitration Guide (found in the docs folder).Regards,/Daniel

  • RELEVANCY SCORE 3.10

    DB:3.10:Scripting Language Esb Action a1



    Purpose: To discuss the design of possible scripting language support in the JBoss ESB (post 4.0 GA)Groovy scripts can already be used inside of the transformation engine. quickstarts\transform_EDI2XML_Groovy_XSLT illustrates this capability.Here are the primary questions to be answered when designing a scripting language ESB action:A- Which scripting languages should be supported? Limit it to Groovy or more?B- Support for Java 5 and Java 6? Java 6 using JSR 223 introduces the javax.scripting package which allows for plug play with various scripting engines: https://scripting.dev.java.net/If Java 5 is a requirement then perhaps we leverage the capabilities of http://jakarta.apache.org/bsf/C- What should the jbossesb.xml look like (here is an example to start the discussions):

    action class="org.jboss.soa.esb.actions.ScriptingAction" name="ScriptingAction"
    property name="scriptEngine" value="MyScriptingEngine"/
    property name="scriptName" value="MyGroovyScript.groovy"/
    /action

    DB:3.10:Scripting Language Esb Action a1


    We have Groovy support and one of our SEs has worked on more general scripting. That's not in the code yet, but it should be soon.

  • RELEVANCY SCORE 3.10

    DB:3.10:Java.Lang.Outofmemoryerror While Processing A File Size With 1s



    Hi,I had modified helloworld_ftp_action example where JBoss ESB reads a file and after processing it will send it to queue. It is reading a file from FTP server with less size (272KB) properly. But when I send file with size around 8MB, then process is failing with following error:run: [echo] Launching Quickstart in standalone mode... [java] +----------------------------------------------------------+ [java] | | [java] | Starting JBossESB... | [java] | | [java] +----------------------------------------------------------+ [java] Reading config from E:\jbossesb-4.2MR3\samples\quickstarts\helloworld_ftp_action\jboss-esb.xml [java] Exception in thread "main" java.lang.OutOfMemoryError: Java heap space BUILD FAILED E:\jbossesb-4.2MR3\samples\quickstarts\conf\base-build.xml:269: Java returned: 1I had increased the heap size in JBoss AS server from default values in run.bat file:set JAVA_OPTS=%JAVA_OPTS% -Xms512m -Xmx1024mBut no use. Do I need to specify it in some other place?.What is the maximum file size that JBoss ESB read messages from FTP server and able to process without any errors?Please pour some inputs.Thanks,-Vidya

    DB:3.10:Java.Lang.Outofmemoryerror While Processing A File Size With 1s


    Hi,Also I had tried with jbossesb-4.0GA version but same error. I am not sure but problem might be with application server jboss-4.0.5.GA.Anyone has faced simillar problem please let me know.Thanks,-Vidya

  • RELEVANCY SCORE 3.10

    DB:3.10:4.2mr1: Jbpm_Simple1 Quickstart : Filenotfoundexception Judd pd



    Hi,I'm using jbossesb-4.2MR1When I run the 'ant clean run' task in the jbpm_simple1 quickstart I get the following exception. [java] 21:56:48,890 DEBUG [main][JbpmContext] closing JbpmContext [java] java.io.FileNotFoundException: D:\java\jbossesb-4.2MR1\samples\quickstarts\jbpm_simple1\..\..\..\..\qa\junit\src\org\jboss\soa\esb\services\registry\juddi-qatest.properties (The system cannot find the path specified) [java] at java.io.FileInputStream.open(Native Method) [java] at java.io.FileInputStream.(FileInputStream.java:106) [java] at java.io.FileInputStream.(FileInputStream.java:66) [java] at quickstart.jbpm_simple1.TestLauncher.runBeforeTest(TestLauncher.java:96) [java] at quickstart.jbpm_simple1.TestLauncher.main(TestLauncher.java:39) [java] We should stop testing, since we don't have a db.The file is missing from the jbossesb-4.2MR1 installation package. It seems like one has to use the code in the svn trunk../ Joakim

    DB:3.10:4.2mr1: Jbpm_Simple1 Quickstart : Filenotfoundexception Judd pd


    I tested the jbpm_simple1 and orcestration quickstarts with MR2.There is an error in build.xml:property="jbpm.services.build.dir" value=${product.dir}/build/services/jbpm.esb"Should beproperty name="jbpm.services.build.dir" value="${product.dir}/lib/jbpm.esb"After this everything works fine. We are blogging about our JBoss ESB testing at http://testingjesb.blogspot.com// Joakim

  • RELEVANCY SCORE 3.10

    DB:3.10:Jboss Esb Integration With Sap 8p



    A client has an existing JBoss ESB platform and is implementing SAP. They would like to leverage their existing SOA and use the ESB to integrate with SAP without implementing SAP XI. I would like to get details around the SAP adapters that the JBoss ESB provides for integration with SAP.Thanks,Deepa

    DB:3.10:Jboss Esb Integration With Sap 8p


    A client has an existing JBoss ESB platform and is implementing SAP. They would like to leverage their existing SOA and use the ESB to integrate with SAP without implementing SAP XI. I would like to get details around the SAP adapters that the JBoss ESB provides for integration with SAP.Thanks,Deepa

  • RELEVANCY SCORE 3.10

    DB:3.10:Calling Stored Procedure From Jboss Esb fd



    Hi,

    Can any one tell me how to call a stored procedure fron Jboss ESB?

    Thanks Regards,

    Anushree

    DB:3.10:Calling Stored Procedure From Jboss Esb fd


    You could implement a custom action.

    I have attached a simple version (including a unit test). It works in a somwhat similar fashion to the ESBProcessor standard action.

    Hope it can be of some help.

  • RELEVANCY SCORE 3.10

    DB:3.10:Jbossas6 + Esb4.10 z7



    I've been trying to integrate JBoss ESB 4.10 into JBoss AS 6 according to [jbossesb-4.10\install\readme.txt].

    And I think ESB does work under JBossAS. Because,

    when I build quick start samples under [jbossesb-4.10\samples\quickstarts] into jboss as, it runs ok.

    Previously, I did a simple POC, it integrates spring and ibatis.

    1. receives message.

    2. transform xml to java bean by using smooks.

    3. restore message into mysql db.

    4. transfer message to another web service.

    This POC runs ok under ESB 4.10 server.

    When I deploy it into jboss as integrated with esb, it cannot start up. Here is the error message.

    DEPLOYMENTS IN ERROR:

    Deployment "vfs:///C:/java/jboss-6.0.0.Final/server/default/deploy/EsbServerTest.esb" is in error due to the following reason(s): java.lang.IllegalArgumentExeption: Null type

    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeloyersImpl.java:1228) [:2.2.0.GA]

    at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MaineployerImpl.java:905) [:2.2.0.GA]

    at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.heckComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]

    at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.chckAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]

    at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]

    at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]

    at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(bstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

    at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.un(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

    at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]

    By the way, why I have to run my POC under JBossAS, because I want to do a POC of ESB that can realize two phase commit of web service transaction.

    And I have builded JBossTS into JBossAS, the xts-demo runs ok now.

    Thanks.

    DB:3.10:Jbossas6 + Esb4.10 z7


    start run.bat, failed.

    please refer to the following logs, thanks.

    boot.log -

    ...............................

    22:23:25,734 INFO [JMXKernel] Legacy JMX core initialized

    22:23:37,593 ERROR [STDERR] log4j:WARN No appenders could be found for logger (org.jboss.soa.esb.listeners.deployers.mc.as6.EsbConfigParser).

    22:23:37,593 ERROR [STDERR] log4j:WARN Please initialize the log4j system properly.

    22:23:39,250 INFO [AbstractServerConfig] JBoss Web Services - Stack CXF Server 3.4.1.GA

    22:23:40,468 INFO [JSFImplManagementDeployer] Initialized 3 JSF configurations: [Mojarra-1.2, MyFaces-2.0, Mojarra-2.0]

    22:23:54,234 警告 [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

    22:24:47,796 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfs:///C:/java/jboss-6.0.0.Final/server/default/deploy/EsbServerTest.esb state=ClassLoader mode=Manual requiredState=PostClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///C:/java/jboss-6.0.0.Final/server/default/deploy/EsbServerTest.esb

    at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.GA]

    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) [:2.2.0.GA]

    at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.GA]

    at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.GA]

    at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]

    at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]

    at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]

    at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]

    at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]

    at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:151) [:0.2.2]

    at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [:0.2.2]

    at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA]

    at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]

    at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.start(ProfileActivationWrapper.java:190) [:0.2.2]

    at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(ProfileActivationWrapper.java:87) [:0.2.2]

    at org.jboss.profileservice.dependency.ProfileActivationService.activateProfile(ProfileActivationService.java:215) [:0.2.2]

    at org.jboss.profileservice.dependency.ProfileActivationService.activate(ProfileActivationService.java:159) [:0.2.2]

    at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:112) [:0.2.2]

    at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:87) [:0.2.2]

    at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91) [:0.2.2]

    at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.0.0.Final]

    at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]

    at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

    at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

    at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]

    Caused by: java.lang.Error: Error visiting "/C:/java/jboss-6.0.0.Final/server/default/deploy/EsbServerTest.esb/lib/com.springsource.org.aspectj.weaver-1.6.8.RELEASE.jar/org/aspectj/weaver/Iterators$4$1.class"

    at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:268) [jboss-classloading-vfs.jar:2.2.0.GA]

    at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:408) [jboss-vfs.jar:3.0.0.GA]

    at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:410) [jboss-vfs.jar:3.0.0.GA]

    at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:410) [jboss-vfs.jar:3.0.0.GA]

    at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:410) [jboss-vfs.jar:3.0.0.GA]

    at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:396) [jboss-vfs.jar:3.0.0.GA]

    at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:102) [jboss-classloading-vfs.jar:2.2.0.GA]

    at org.jboss.deployers.vfs.plugins.classloader.VFSDeploymentClassLoaderPolicyModule.visit(VFSDeploymentClassLoaderPolicyModule.java:181) [:2.2.0.GA]

    at org.jboss.scanning.plugins.DeploymentUnitScanner.scan(DeploymentUnitScanner.java:111) [:1.0.0.GA]

    at org.jboss.scanning.spi.helpers.UrlScanner.scan(UrlScanner.java:96) [:1.0.0.GA]

    at org.jboss.scanning.deployers.ScanningDeployer.deploy(ScanningDeployer.java:95) [:1.0.0.GA]

    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA]

    ... 43 more

    Caused by: java.lang.RuntimeException: Error visiting resource: VFSResourceContext @ org/aspectj/weaver/Iterators$4$1.class / BaseClassLoader@3a0533{vfs:///C:/java/jboss-6.0.0.Final/server/default/deploy/EsbServerTest.esb}, visitor: org.jboss.scanning.annotations.plugins.GenericAnnotationVisitor@110e291

    at org.jboss.scanning.plugins.visitor.IgnoreSetErrorHandler.handleError(IgnoreSetErrorHandler.java:56) [:1.0.0.GA]

    at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:91) [:1.0.0.GA]

    at org.jboss.scanning.annotations.plugins.AnnotationsScanningPlugin.visit(AnnotationsScanningPlugin.java:89) [:1.0.0.GA]

    at org.jboss.scanning.spi.helpers.ScanningPluginWrapper.visit(ScanningPluginWrapper.java:112) [:1.0.0.GA]

    at org.jboss.classloading.plugins.visitor.FederatedResourceVisitor.visit(FederatedResourceVisitor.java:101) [jboss-classloading.jar:2.2.0.GA]

    at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:264) [jboss-classloading-vfs.jar:2.2.0.GA]

    ... 54 more

    Caused by: java.lang.IllegalArgumentException: Null type

    at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getTypeInfo(IntrospectionTypeInfoFactoryImpl.java:354) [jboss-reflect.jar:2.2.0.GA]

    at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl$2.run(IntrospectionTypeInfoFactoryImpl.java:230) [jboss-reflect.jar:2.2.0.GA]

    at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl$2.run(IntrospectionTypeInfoFactoryImpl.java:218) [jboss-reflect.jar:2.2.0.GA]

    at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_22]

    at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getMethods(IntrospectionTypeInfoFactoryImpl.java:217) [jboss-reflect.jar:2.2.0.GA]

    at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredMethods(ClassInfoImpl.java:416) [jboss-reflect.jar:2.2.0.GA]

    at org.jboss.scanning.plugins.visitor.ClassHierarchyResourceVisitor.handleClass(ClassHierarchyResourceVisitor.java:80) [:1.0.0.GA]

    at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.doVisit(ReflectResourceVisitor.java:108) [:1.0.0.GA]

    at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:86) [:1.0.0.GA]

    ... 58 more

    22:24:51,437 INFO [InVMTemporaryTransport] Starting reaper thread

    22:24:52,687 INFO [MetadataBuilder] Add Service

    ...................

    server.log -

    2011-08-31 22:26:30,671 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (Thread-2) Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=JBossESBDS' to JNDI name 'java:JBossESBDS'

    2011-08-31 22:26:30,671 INFO [org.jboss.internal.soa.esb.dependencies.DatabaseInitializer] (Thread-2) java:/JBossESBDS datasource is already initialized

    2011-08-31 22:26:31,203 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] (Thread-2) Starting ESB Deployment 'jbossesb.esb'

    2011-08-31 22:26:31,750 INFO [org.jboss.internal.soa.esb.persistence.manager.J2eeConnectionManager] (Thread-2) initializing...

    2011-08-31 22:26:31,765 INFO [org.jboss.soa.esb.message.MessagePayloadProxy] (Thread-2) Using the non-legacy payload-to-message exchange pattern. To switch back to the legacy exchange patterns, use the 'core:use.legacy.message.payload.exchange.patterns' property in jbossesb-properties.xml.

    2011-08-31 22:26:32,921 INFO [org.apache.juddi.api.impl.InquiryHelper] (pool-9-thread-3) uddi:juddi.apache.org:a9f946ff-d096-4fee-9824-8b052ddfdbe2 is modified Mon Aug 29 23:22:56 CST 2011 1314631376781

    2011-08-31 22:26:33,250 INFO [org.quartz.core.SchedulerSignalerImpl] (Thread-2) Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl

    2011-08-31 22:26:33,250 INFO [org.quartz.core.QuartzScheduler] (Thread-2) Quartz Scheduler v.1.8.3 created.

    2011-08-31 22:26:33,250 INFO [org.quartz.simpl.RAMJobStore] (Thread-2) RAMJobStore initialized.

    2011-08-31 22:26:33,250 INFO [org.quartz.core.QuartzScheduler] (Thread-2) Scheduler meta-data: Quartz Scheduler (v1.8.3) 'ESBScheduler:jbossesb.esb' with instanceId 'NON_CLUSTERED'

    Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.

    NOT STARTED.

    Currently in standby mode.

    Number of jobs executed: 0

    Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 1 threads.

    Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

    2011-08-31 22:26:33,250 INFO [org.quartz.impl.StdSchedulerFactory] (Thread-2) Quartz scheduler 'ESBScheduler:jbossesb.esb' initialized from an externally provided properties instance.

    2011-08-31 22:26:33,250 INFO [org.quartz.impl.StdSchedulerFactory] (Thread-2) Quartz scheduler version: 1.8.3

    2011-08-31 22:26:33,250 INFO [org.quartz.core.QuartzScheduler] (Thread-2) Scheduler ESBScheduler:jbossesb.esb_$_NON_CLUSTERED started.

    2011-08-31 22:26:34,937 INFO [org.jboss.internal.soa.esb.dependencies.H2Database] (Thread-2) jdbc:h2:file:/C:/java/jboss-6.0.0.Final/server/default/data/h2/jbpmDB;MVCC=TRUE;DB_CLOSE_ON_EXIT=FALSE

    2011-08-31 22:26:35,687 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (Thread-2) Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=JbpmDS' to JNDI name 'java:JbpmDS'

    2011-08-31 22:26:35,750 INFO [org.jboss.internal.soa.esb.dependencies.DatabaseInitializer] (Thread-2) java:/JbpmDS datasource is already initialized

    2011-08-31 22:26:35,765 INFO [org.jbpm.JbpmConfiguration] (Thread-2) using configuration resource: jbpm.cfg.xml

    2011-08-31 22:26:35,796 INFO [org.jbpm.persistence.db.StaleObjectLogConfigurer] (Thread-2) stale object exceptions will be hidden from logging

    2011-08-31 22:26:35,906 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) configuring from resource: hibernate.cfg.xml

    2011-08-31 22:26:35,906 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Configuration resource: hibernate.cfg.xml

    2011-08-31 22:26:35,921 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:35,937 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : hibernate.extra.hbm.xml

    2011-08-31 22:26:35,937 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] (Thread-2) Starting ESB Deployment 'jbpm.esb'

    2011-08-31 22:26:35,937 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:35,968 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : hibernate.identity.hbm.xml

    2011-08-31 22:26:35,968 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,015 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/db/hibernate.queries.hbm.xml

    2011-08-31 22:26:36,109 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,125 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/db/hibernate.types.hbm.xml

    2011-08-31 22:26:36,125 INFO [org.jboss.soa.esb.services.jbpm.actions.JBpmCallback] (Thread-2) initialise() invoked - config=action action="action" class="org.jboss.soa.esb.services.jbpm.actions.JBpmCallback"/

    2011-08-31 22:26:36,140 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,140 INFO [org.apache.juddi.api.impl.InquiryHelper] (pool-9-thread-7) uddi:juddi.apache.org:a7c8ec59-2be9-43ca-b89d-9b480d1ab7be is modified Mon Aug 29 23:23:04 CST 2011 1314631384531

    2011-08-31 22:26:36,156 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/action/MailAction.hbm.xml

    2011-08-31 22:26:36,171 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,187 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/def/ProcessDefinition.hbm.xml

    2011-08-31 22:26:36,203 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,265 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/def/Node.hbm.xml

    2011-08-31 22:26:36,281 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,390 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/def/Transition.hbm.xml

    2011-08-31 22:26:36,390 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,453 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/def/Event.hbm.xml

    2011-08-31 22:26:36,609 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,609 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/def/Action.hbm.xml

    2011-08-31 22:26:36,625 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,640 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/def/SuperState.hbm.xml

    2011-08-31 22:26:36,640 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,656 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/def/ExceptionHandler.hbm.xml

    2011-08-31 22:26:36,656 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,656 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (Thread-2) deploy, ctxPath=/jbpm-console

    2011-08-31 22:26:36,671 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/instantiation/Delegation.hbm.xml

    2011-08-31 22:26:36,796 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,796 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/action/Script.hbm.xml

    2011-08-31 22:26:36,875 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,890 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/StartState.hbm.xml

    2011-08-31 22:26:36,921 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,921 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/EndState.hbm.xml

    2011-08-31 22:26:36,921 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:36,937 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/ProcessState.hbm.xml

    2011-08-31 22:26:37,046 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,062 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/Decision.hbm.xml

    2011-08-31 22:26:37,062 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,078 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/Fork.hbm.xml

    2011-08-31 22:26:37,093 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,234 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/Join.hbm.xml

    2011-08-31 22:26:37,265 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,265 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/MailNode.hbm.xml

    2011-08-31 22:26:37,328 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,343 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/State.hbm.xml

    2011-08-31 22:26:37,359 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,375 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/node/TaskNode.hbm.xml

    2011-08-31 22:26:37,375 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,390 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/def/ContextDefinition.hbm.xml

    2011-08-31 22:26:37,390 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,390 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/def/VariableAccess.hbm.xml

    2011-08-31 22:26:37,406 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,406 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/bytes/ByteArray.hbm.xml

    2011-08-31 22:26:37,406 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,421 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/module/def/ModuleDefinition.hbm.xml

    2011-08-31 22:26:37,421 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,421 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/file/def/FileDefinition.hbm.xml

    2011-08-31 22:26:37,437 信息 [javax.enterprise.resource.webcontainer.jsf.config] (Thread-2) 初始化上下文 '/jbpm-console' 的 Mojarra 2.0.3 ( b05)

    2011-08-31 22:26:37,437 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,437 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/def/TaskMgmtDefinition.hbm.xml

    2011-08-31 22:26:37,437 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,453 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/def/Swimlane.hbm.xml

    2011-08-31 22:26:37,453 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,453 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/def/Task.hbm.xml

    2011-08-31 22:26:37,468 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,468 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/def/TaskController.hbm.xml

    2011-08-31 22:26:37,484 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,484 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/scheduler/def/CreateTimerAction.hbm.xml

    2011-08-31 22:26:37,515 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,515 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/scheduler/def/CancelTimerAction.hbm.xml

    2011-08-31 22:26:37,531 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,531 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/exe/Comment.hbm.xml

    2011-08-31 22:26:37,531 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,546 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/exe/ProcessInstance.hbm.xml

    2011-08-31 22:26:37,546 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,546 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/exe/Token.hbm.xml

    2011-08-31 22:26:37,562 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,562 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/exe/RuntimeAction.hbm.xml

    2011-08-31 22:26:37,562 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,578 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/module/exe/ModuleInstance.hbm.xml

    2011-08-31 22:26:37,578 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,593 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/ContextInstance.hbm.xml

    2011-08-31 22:26:37,828 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,843 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/TokenVariableMap.hbm.xml

    2011-08-31 22:26:37,843 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,843 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/VariableInstance.hbm.xml

    2011-08-31 22:26:37,859 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,859 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/variableinstance/ByteArrayInstance.hbm.xml

    2011-08-31 22:26:37,890 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,890 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/variableinstance/DateInstance.hbm.xml

    2011-08-31 22:26:37,890 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,906 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/variableinstance/DoubleInstance.hbm.xml

    2011-08-31 22:26:37,906 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,921 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/variableinstance/HibernateLongInstance.hbm.xml

    2011-08-31 22:26:37,921 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,921 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/variableinstance/HibernateStringInstance.hbm.xml

    2011-08-31 22:26:37,921 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,937 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/variableinstance/LongInstance.hbm.xml

    2011-08-31 22:26:37,937 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,953 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/variableinstance/NullInstance.hbm.xml

    2011-08-31 22:26:37,953 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,953 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/exe/variableinstance/StringInstance.hbm.xml

    2011-08-31 22:26:37,968 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:37,968 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/job/Job.hbm.xml

    2011-08-31 22:26:38,000 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,000 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/job/Timer.hbm.xml

    2011-08-31 22:26:38,015 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,015 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/job/ExecuteNodeJob.hbm.xml

    2011-08-31 22:26:38,015 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,031 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/job/ExecuteActionJob.hbm.xml

    2011-08-31 22:26:38,046 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,046 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/job/CleanUpProcessJob.hbm.xml

    2011-08-31 22:26:38,046 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,046 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/exe/TaskMgmtInstance.hbm.xml

    2011-08-31 22:26:38,062 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,093 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/exe/TaskInstance.hbm.xml

    2011-08-31 22:26:38,296 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,296 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/exe/PooledActor.hbm.xml

    2011-08-31 22:26:38,312 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,328 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/exe/SwimlaneInstance.hbm.xml

    2011-08-31 22:26:38,328 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,328 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/logging/log/ProcessLog.hbm.xml

    2011-08-31 22:26:38,343 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,343 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/logging/log/MessageLog.hbm.xml

    2011-08-31 22:26:38,343 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,359 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/logging/log/CompositeLog.hbm.xml

    2011-08-31 22:26:38,359 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,359 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/ActionLog.hbm.xml

    2011-08-31 22:26:38,359 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,375 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/NodeLog.hbm.xml

    2011-08-31 22:26:38,375 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,375 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/ProcessInstanceCreateLog.hbm.xml

    2011-08-31 22:26:38,390 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,390 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/ProcessInstanceEndLog.hbm.xml

    2011-08-31 22:26:38,390 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,406 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/ProcessStateLog.hbm.xml

    2011-08-31 22:26:38,406 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,406 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/SignalLog.hbm.xml

    2011-08-31 22:26:38,406 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,421 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/TokenCreateLog.hbm.xml

    2011-08-31 22:26:38,421 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,421 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/TokenEndLog.hbm.xml

    2011-08-31 22:26:38,437 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,437 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/graph/log/TransitionLog.hbm.xml

    2011-08-31 22:26:38,453 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,453 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/VariableLog.hbm.xml

    2011-08-31 22:26:38,484 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,500 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/VariableCreateLog.hbm.xml

    2011-08-31 22:26:38,500 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,500 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/VariableDeleteLog.hbm.xml

    2011-08-31 22:26:38,500 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,515 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/VariableUpdateLog.hbm.xml

    2011-08-31 22:26:38,515 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,531 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/variableinstance/ByteArrayUpdateLog.hbm.xml

    2011-08-31 22:26:38,734 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,734 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/variableinstance/DateUpdateLog.hbm.xml

    2011-08-31 22:26:38,750 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,750 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/variableinstance/DoubleUpdateLog.hbm.xml

    2011-08-31 22:26:38,750 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,765 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/variableinstance/HibernateLongUpdateLog.hbm.xml

    2011-08-31 22:26:38,765 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,765 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/variableinstance/HibernateStringUpdateLog.hbm.xml

    2011-08-31 22:26:38,765 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,781 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/variableinstance/LongUpdateLog.hbm.xml

    2011-08-31 22:26:38,781 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,781 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/context/log/variableinstance/StringUpdateLog.hbm.xml

    2011-08-31 22:26:38,796 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,796 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/log/TaskLog.hbm.xml

    2011-08-31 22:26:38,796 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,812 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/log/TaskCreateLog.hbm.xml

    2011-08-31 22:26:38,859 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,875 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/log/TaskAssignLog.hbm.xml

    2011-08-31 22:26:38,875 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,875 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/log/TaskEndLog.hbm.xml

    2011-08-31 22:26:38,890 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,890 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/log/SwimlaneLog.hbm.xml

    2011-08-31 22:26:38,890 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,906 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/log/SwimlaneCreateLog.hbm.xml

    2011-08-31 22:26:38,906 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,906 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Reading mappings from resource : org/jbpm/taskmgmt/log/SwimlaneAssignLog.hbm.xml

    2011-08-31 22:26:38,906 WARN [org.hibernate.util.DTDEntityResolver] (JbpmJobExector:192.168.1.100:1) recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!

    2011-08-31 22:26:38,921 INFO [org.hibernate.cfg.Configuration] (JbpmJobExector:192.168.1.100:1) Configured SessionFactory: null

    2011-08-31 22:26:38,937 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.identity.User - JBPM_ID_USER

    2011-08-31 22:26:39,000 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.identity.User.permissions - JBPM_ID_PERMISSIONS

    2011-08-31 22:26:39,000 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.identity.Group - JBPM_ID_GROUP

    2011-08-31 22:26:39,171 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.identity.Group.permissions - JBPM_ID_PERMISSIONS

    2011-08-31 22:26:39,171 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.identity.Membership - JBPM_ID_MEMBERSHIP

    2011-08-31 22:26:39,171 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.identity.Membership.permissions - JBPM_ID_PERMISSIONS

    2011-08-31 22:26:39,171 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.def.ProcessDefinition - JBPM_PROCESSDEFINITION

    2011-08-31 22:26:39,312 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.def.Node - JBPM_NODE

    2011-08-31 22:26:39,390 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.def.Transition - JBPM_TRANSITION

    2011-08-31 22:26:39,390 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.def.Event - JBPM_EVENT

    2011-08-31 22:26:39,390 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.def.Action - JBPM_ACTION

    2011-08-31 22:26:39,453 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.def.SuperState - JBPM_NODE

    2011-08-31 22:26:39,453 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.def.ExceptionHandler - JBPM_EXCEPTIONHANDLER

    2011-08-31 22:26:39,453 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.instantiation.Delegation - JBPM_DELEGATION

    2011-08-31 22:26:39,453 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.action.Script - JBPM_ACTION

    2011-08-31 22:26:39,453 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.StartState - JBPM_NODE

    2011-08-31 22:26:39,453 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.EndState - JBPM_NODE

    2011-08-31 22:26:39,453 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.ProcessState - JBPM_NODE

    2011-08-31 22:26:39,468 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.Decision - JBPM_NODE

    2011-08-31 22:26:39,468 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.node.Decision.decisionConditions - JBPM_DECISIONCONDITIONS

    2011-08-31 22:26:39,468 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.Fork - JBPM_NODE

    2011-08-31 22:26:39,484 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.Join - JBPM_NODE

    2011-08-31 22:26:39,484 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.MailNode - JBPM_NODE

    2011-08-31 22:26:39,484 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.State - JBPM_NODE

    2011-08-31 22:26:39,484 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.node.TaskNode - JBPM_NODE

    2011-08-31 22:26:39,625 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.context.def.VariableAccess - JBPM_VARIABLEACCESS

    2011-08-31 22:26:39,625 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.bytes.ByteArray - JBPM_BYTEARRAY

    2011-08-31 22:26:39,625 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.bytes.ByteArray.byteBlocks - JBPM_BYTEBLOCK

    2011-08-31 22:26:39,625 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.module.def.ModuleDefinition - JBPM_MODULEDEFINITION

    2011-08-31 22:26:39,625 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.file.def.FileDefinition - JBPM_MODULEDEFINITION

    2011-08-31 22:26:39,625 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.def.TaskMgmtDefinition - JBPM_MODULEDEFINITION

    2011-08-31 22:26:39,625 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.taskmgmt.def.Swimlane - JBPM_SWIMLANE

    2011-08-31 22:26:39,640 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.taskmgmt.def.Task - JBPM_TASK

    2011-08-31 22:26:39,640 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.taskmgmt.def.TaskController - JBPM_TASKCONTROLLER

    2011-08-31 22:26:39,640 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.scheduler.def.CreateTimerAction - JBPM_ACTION

    2011-08-31 22:26:39,640 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.scheduler.def.CancelTimerAction - JBPM_ACTION

    2011-08-31 22:26:39,640 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.exe.Comment - JBPM_COMMENT

    2011-08-31 22:26:39,656 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.exe.ProcessInstance - JBPM_PROCESSINSTANCE

    2011-08-31 22:26:39,656 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.exe.Token - JBPM_TOKEN

    2011-08-31 22:26:39,656 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.graph.exe.RuntimeAction - JBPM_RUNTIMEACTION

    2011-08-31 22:26:39,671 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.module.exe.ModuleInstance - JBPM_MODULEINSTANCE

    2011-08-31 22:26:39,671 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.ContextInstance - JBPM_MODULEINSTANCE

    2011-08-31 22:26:39,671 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.context.exe.TokenVariableMap - JBPM_TOKENVARIABLEMAP

    2011-08-31 22:26:39,671 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.context.exe.VariableInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,718 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.variableinstance.ByteArrayInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.variableinstance.DateInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.variableinstance.DoubleInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.variableinstance.HibernateLongInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.variableinstance.HibernateStringInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.variableinstance.LongInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.variableinstance.NullInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.exe.variableinstance.StringInstance - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.job.Job - JBPM_JOB

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.job.Timer - JBPM_JOB

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.job.ExecuteNodeJob - JBPM_JOB

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.job.ExecuteActionJob - JBPM_JOB

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.job.CleanUpProcessJob - JBPM_JOB

    2011-08-31 22:26:39,734 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.exe.TaskMgmtInstance - JBPM_MODULEINSTANCE

    2011-08-31 22:26:39,750 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.taskmgmt.exe.TaskInstance - JBPM_TASKINSTANCE

    2011-08-31 22:26:39,750 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.exe.TaskInstance.pooledActors - JBPM_TASKACTORPOOL

    2011-08-31 22:26:39,750 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.taskmgmt.exe.PooledActor - JBPM_POOLEDACTOR

    2011-08-31 22:26:39,750 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.exe.PooledActor.taskInstances - JBPM_TASKACTORPOOL

    2011-08-31 22:26:39,750 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.taskmgmt.exe.SwimlaneInstance - JBPM_SWIMLANEINSTANCE

    2011-08-31 22:26:39,781 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping class: org.jbpm.logging.log.ProcessLog - JBPM_LOG

    2011-08-31 22:26:39,781 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.logging.log.MessageLog - JBPM_LOG

    2011-08-31 22:26:39,781 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.logging.log.CompositeLog - JBPM_LOG

    2011-08-31 22:26:39,781 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.ActionLog - JBPM_LOG

    2011-08-31 22:26:39,781 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.NodeLog - JBPM_LOG

    2011-08-31 22:26:39,781 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.ProcessInstanceCreateLog - JBPM_LOG

    2011-08-31 22:26:39,781 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.ProcessInstanceEndLog - JBPM_LOG

    2011-08-31 22:26:39,781 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.ProcessStateLog - JBPM_LOG

    2011-08-31 22:26:39,796 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.SignalLog - JBPM_LOG

    2011-08-31 22:26:39,796 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.TokenCreateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.TokenEndLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.log.TransitionLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.VariableLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.VariableCreateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.VariableDeleteLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.VariableUpdateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.variableinstance.ByteArrayUpdateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.variableinstance.DateUpdateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.variableinstance.DoubleUpdateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.variableinstance.HibernateLongUpdateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.variableinstance.HibernateStringUpdateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.variableinstance.LongUpdateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.log.variableinstance.StringUpdateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.log.TaskLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.log.TaskCreateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.log.TaskAssignLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.log.TaskEndLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.log.SwimlaneLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.log.SwimlaneCreateLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.taskmgmt.log.SwimlaneAssignLog - JBPM_LOG

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.graph.action.MailAction - JBPM_ACTION

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping subclass: org.jbpm.context.def.ContextDefinition - JBPM_MODULEDEFINITION

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.identity.User.memberships - JBPM_ID_MEMBERSHIP

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.identity.Group.children - JBPM_ID_GROUP

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.identity.Group.memberships - JBPM_ID_MEMBERSHIP

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.ProcessDefinition.events - JBPM_EVENT

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.ProcessDefinition.exceptionHandlers - JBPM_EXCEPTIONHANDLER

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.ProcessDefinition.nodes - JBPM_NODE

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.ProcessDefinition.actions - JBPM_ACTION

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.ProcessDefinition.definitions - JBPM_MODULEDEFINITION

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.Node.events - JBPM_EVENT

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.Node.exceptionHandlers - JBPM_EXCEPTIONHANDLER

    2011-08-31 22:26:39,812 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.Node.leavingTransitions - JBPM_TRANSITION

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.Node.arrivingTransitions - JBPM_TRANSITION

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.Transition.events - JBPM_EVENT

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.Transition.exceptionHandlers - JBPM_EXCEPTIONHANDLER

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.Event.actions - JBPM_ACTION

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.SuperState.nodes - JBPM_NODE

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.def.ExceptionHandler.actions - JBPM_ACTION

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.action.Script.variableAccesses - JBPM_VARIABLEACCESS

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.node.ProcessState.variableAccesses - JBPM_VARIABLEACCESS

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.node.TaskNode.tasks - JBPM_TASK

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.file.def.FileDefinition.processFiles - JBPM_BYTEARRAY

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.def.TaskMgmtDefinition.swimlanes - JBPM_SWIMLANE

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.def.TaskMgmtDefinition.tasks - JBPM_TASK

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.def.Swimlane.tasks - JBPM_TASK

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.def.Task.events - JBPM_EVENT

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.def.Task.exceptionHandlers - JBPM_EXCEPTIONHANDLER

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.def.TaskController.variableAccesses - JBPM_VARIABLEACCESS

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.exe.ProcessInstance.runtimeActions - JBPM_RUNTIMEACTION

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.exe.ProcessInstance.instances - JBPM_MODULEINSTANCE

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.exe.Token.children - JBPM_TOKEN

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.graph.exe.Token.comments - JBPM_COMMENT

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.context.exe.ContextInstance.tokenVariableMaps - JBPM_TOKENVARIABLEMAP

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.context.exe.TokenVariableMap.variableInstances - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.exe.TaskMgmtInstance.swimlaneInstances - JBPM_SWIMLANEINSTANCE

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.exe.TaskMgmtInstance.taskInstances - JBPM_TASKINSTANCE

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.exe.TaskInstance.variableInstances - JBPM_VARIABLEINSTANCE

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.exe.TaskInstance.comments - JBPM_COMMENT

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.taskmgmt.exe.SwimlaneInstance.pooledActors - JBPM_POOLEDACTOR

    2011-08-31 22:26:39,828 INFO [org.hibernate.cfg.HbmBinder] (JbpmJobExector:192.168.1.100:1) Mapping collection: org.jbpm.logging.log.CompositeLog.children - JBPM_LOG

    2011-08-31 22:26:39,968 INFO [org.quartz.utils.UpdateChecker] (Timer-2) New Quartz update(s) found: 1.8.5 [http://www.terracotta.org/kit/reflector?kitID=defaultpageID=QuartzChangeLog]

    2011-08-31 22:26:40,171 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] (JbpmJobExector:192.168.1.100:1) Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.

    2011-08-31 22:26:40,296 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] (JbpmJobExector:192.168.1.100:1) Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.

    2011-08-31 22:26:40,296 INFO [org.hibernate.cfg.search.HibernateSearchEventListenerRegister] (JbpmJobExector:192.168.1.100:1) Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled.

    2011-08-31 22:26:40,359 INFO [org.hibernate.util.NamingHelper] (JbpmJobExector:192.168.1.100:1) JNDI InitialContext properties:{}

    2011-08-31 22:26:40,375 INFO [org.hibernate.connection.DatasourceConnectionProvider] (JbpmJobExector:192.168.1.100:1) Using datasource: java:/JbpmDS

    2011-08-31 22:26:40,421 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Database -

    name : H2

    version : 1.2.124 (2009-11-20)

    major : 1

    minor : 2

    2011-08-31 22:26:40,421 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Driver -

    name : H2 JDBC Driver

    version : 1.2.124 (2009-11-20)

    major : 1

    minor : 2

    2011-08-31 22:26:40,421 INFO [org.hibernate.dialect.Dialect] (JbpmJobExector:192.168.1.100:1) Using dialect: org.hibernate.dialect.HSQLDialect

    2011-08-31 22:26:40,437 INFO [org.hibernate.engine.jdbc.JdbcSupportLoader] (JbpmJobExector:192.168.1.100:1) Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4

    2011-08-31 22:26:40,437 INFO [org.hibernate.transaction.TransactionFactoryFactory] (JbpmJobExector:192.168.1.100:1) Transaction strategy: org.hibernate.transaction.JTATransactionFactory

    2011-08-31 22:26:40,437 INFO [org.hibernate.util.NamingHelper] (JbpmJobExector:192.168.1.100:1) JNDI InitialContext properties:{}

    2011-08-31 22:26:40,437 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] (JbpmJobExector:192.168.1.100:1) instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup

    2011-08-31 22:26:40,453 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] (JbpmJobExector:192.168.1.100:1) instantiated TransactionManagerLookup

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Automatic flush during beforeCompletion(): disabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Automatic session close at end of transaction: disabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) JDBC batch size: 15

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) JDBC batch updates for versioned data: disabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Scrollable result sets: enabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) JDBC3 getGeneratedKeys(): enabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Connection release mode: auto

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Default batch fetch size: 1

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Generate SQL with comments: disabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Order SQL updates by primary key: disabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Order SQL inserts for batching: disabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory

    2011-08-31 22:26:40,453 INFO [org.hibernate.hql.ast.ASTQueryTranslatorFactory] (JbpmJobExector:192.168.1.100:1) Using ASTQueryTranslatorFactory

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Query language substitutions: {}

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) JPA-QL strict compliance: disabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Second-level cache: enabled

    2011-08-31 22:26:40,453 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Query cache: disabled

    2011-08-31 22:26:40,468 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Cache region factory : org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge

    2011-08-31 22:26:40,484 INFO [org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge] (JbpmJobExector:192.168.1.100:1) Cache provider: org.hibernate.cache.HashtableCacheProvider

    2011-08-31 22:26:40,484 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Optimize cache for minimal puts: disabled

    2011-08-31 22:26:40,484 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Structured second-level cache entries: disabled

    2011-08-31 22:26:40,484 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Statistics: disabled

    2011-08-31 22:26:40,484 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Deleted entity synthetic identifier rollback: disabled

    2011-08-31 22:26:40,500 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Default entity-mode: pojo

    2011-08-31 22:26:40,500 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Named query checking : enabled

    2011-08-31 22:26:40,500 INFO [org.hibernate.cfg.SettingsFactory] (JbpmJobExector:192.168.1.100:1) Check Nullability in Core (should be disabled when Bean Validation is on): disabled

    2011-08-31 22:26:40,515 INFO [org.hibernate.impl.SessionFactoryImpl] (JbpmJobExector:192.168.1.100:1) building session factory

    2011-08-31 22:26:41,843 INFO [org.hibernate.impl.SessionFactoryObjectFactory] (JbpmJobExector:192.168.1.100:1) Not binding factory to JNDI, no JNDI name configured

    2011-08-31 22:26:41,843 INFO [org.hibernate.util.NamingHelper] (JbpmJobExector:192.168.1.100:1) JNDI InitialContext properties:{}

    2011-08-31 22:26:42,984 INFO [org.jboss.internal.soa.esb.services.rules.LogSystemEventListener] (Thread-2) Message [ResourceChangeNotification created]

    2011-08-31 22:26:42,984 INFO [org.jboss.internal.soa.esb.services.rules.LogSystemEventListener] (Thread-24) Message [ResourceChangeNotification has started listening for ChangeSet publications]

    2011-08-31 22:26:43,000 INFO [org.jboss.internal.soa.esb.services.rules.LogSystemEventListener] (Thread-2) Message [ResourceChangeScanner reconfigured with interval=60]

    2011-08-31 22:26:43,000 INFO [org.jboss.internal.soa.esb.services.rules.LogSystemEventListener] (Thread-2) Message [ResourceChangeScanner created with default interval=60]

    2011-08-31 22:26:43,000 INFO [org.jboss.internal.soa.esb.services.rules.DroolsResourceChangeService] (Thread-2) setting drools.resource.scanner.interval to 60

    2011-08-31 22:26:43,000 INFO [org.jboss.internal.soa.esb.services.rules.LogSystemEventListener] (Thread-2) Message [ResourceChangeScanner reconfigured with interval=60]

    2011-08-31 22:26:43,000 INFO [org.jboss.internal.soa.esb.services.rules.LogSystemEventListener] (Thread-2) Message [ResourceChangeScanner reconfigured with interval=60]

    2011-08-31 22:26:43,000 INFO [org.jboss.internal.soa.esb.services.rules.LogSystemEventListener] (Thread-25) Message [ResourceChangeNotification scanner has started]

    2011-08-31 22:26:43,031 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] (Thread-2) Starting ESB Deployment 'jbrules.esb'

    2011-08-31 22:26:43,046 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] (Thread-2) Starting ESB Deployment 'slsb.esb'

    2011-08-31 22:26:43,062 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] (Thread-2) Starting ESB Deployment 'smooks.esb'

    2011-08-31 22:26:43,109 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] (Thread-2) Starting ESB Deployment 'soap.esb'

    2011-08-31 22:26:43,125 INFO [org.jboss.soa.esb.listeners.deployers.mc.as6.EsbDeployment] (Thread-2) Starting ESB Deployment 'spring.esb'

    2011-08-31 22:26:43,203 ERROR [ProfileServiceBootstrap] (Thread-2) Failed to load profile:: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

    DEPLOYMENTS IN ERROR:

    Deployment "vfs:///C:/java/jboss-6.0.0.Final/server/default/deploy/EsbServerTest.esb" is in error due to the following reason(s): java.lang.IllegalArgumentException: Null type

    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA]

    at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]

    at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]

    at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]

    at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]

    at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]

    at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

    at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

    at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]

    2011-08-31 22:26:43,250 INFO [org.apache.coyote.http11.Http11Protocol] (Thread-2) Starting Coyote HTTP/1.1 on http-127.0.0.1-8080

    2011-08-31 22:26:43,250 INFO [org.apache.coyote.ajp.AjpProtocol] (Thread-2) Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009

    2011-08-31 22:26:43,250 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] (Thread-2) JBossAS [6.0.0.Final "Neo"] Started in 3m:20s:110ms

  • RELEVANCY SCORE 3.10

    DB:3.10:How To Expose Esb As A Webservice With Soap Over Https. a7



    Hi All,

    In quickstarts i found a way to expose esb service as a webservice using SOAP over http but

    I have a requirement of expoing esb service as a webservice using SOAP over https.

    Please help if anybody has already worked on it.

    Thanks,

    Ravi

    DB:3.10:How To Expose Esb As A Webservice With Soap Over Https. a7


    Thanks Magesh, the actual requirement is to expose an esb as webservice using soap over https and as per my understanding I need to use Jboss ws to use a SOAPProcessor.

    I need EBWS over HTTPS to solve the requirement. I would be checking the JIRA for updates on it.

    Thanks,

    Ravi

  • RELEVANCY SCORE 3.10

    DB:3.10:Problems With Quickstart Webservice_Consumer1 98



    I try to run the webservice_consumer1 quickstart.What I've done so far:1) installed JBoss AS 4.2.12) deployed JBoss ESB 4.23) deployed JBoss WS native 2.0.1So far everything works fine, but the quickstart needs some additional stuff, so it won't work:BUILD FAILEDC:\jbossesb-4.2GA\samples\quickstarts\conf\base-build.xml:435: ****DEPLOYMENT FAILED... Sorry, this Quickstart requires a modified JBoss Webservice container, please refer to the 'Configuring Webservice Integration' section of the Administration Guide.As soon as I do what is told me and patch JBossWS ('ant patch-jbossws') I get some serious errors at the startup of the AS and the quickstart still won't work.
    15:44:57,421 ERROR [URLDeploymentScanner] Incomplete Deployment listing:--- MBeans waiting for other MBeans ---ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbossws.sar#jbossws.beans' State: FAILED Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelDeployment@87cd5c{name=file:/C:/JBoss_AS_4.2.1/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml[......]*** DEPLOYMENTS IN ERROR:WSWebMetaDataAdapter - java.lang.NoClassDefFoundError: org/jboss/wsf/container/jboss42/WebMetaDataAdapterWSEndpointJAXBIntrosCustomizationsDeployer - java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/AbstractDeployer*** DEPLOYMENTS MISSING DEPENDENCIES:WSNativeDeploymentAspectInstallerPostJSE - WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}[.......]I shortened the errors drastically. You can see the whole error message here: http://www.jboss.com/index.html?module=bbop=viewtopicp=4098331 By the way: I can deploy the example successfully but http://localhost:8080/jbossws/ shows no deployed service. I have to get this working. Every help is appreciated!

    DB:3.10:Problems With Quickstart Webservice_Consumer1 98


    I've downloaded the GA version, and when I run the example, and try to access the contract of the webservice (clicking at the contract on the screen) an exception is thrown:

    org.apache.jasper.JasperException: An exception occurred processing JSP page /contract.jsp at line 50

    47: ContractPublisher contractPublisher = publisher.getContractPublisher();
    48:
    49: if(contractPublisher instanceof WebserviceContractPublisher) {
    50: contractInfo = ((WebserviceContractPublisher)contractPublisher).getContractInfo(epr, request);
    51: } else {
    52: contractInfo = contractPublisher.getContractInfo(epr);
    53: }

    Stacktrace:
    org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:518)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:429)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

    root cause

    java.lang.NullPointerException
    org.jboss.soa.esb.actions.soap.WebserviceContractPublisher.getContractInfo(WebserviceContractPublisher.java:104)
    org.apache.jsp.contract_jsp._jspService(contract_jsp.java:113)
    org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

  • RELEVANCY SCORE 3.09

    DB:3.09:Build Failed About Jboss Esb Sample Quickstarts Helloworld 1z



    Hello,

    I am new to JBoss ESB.

    There are two question I confused.

    The first question:

    I downloaded SOA 5.1.0 GA and followed the step in JBoss_Enterprise_SOA_Platform-5-SOA_Getting_Started_Guide-en-US.pdf

    But when I launch the server, it can launch successfully, but it has a warning as below:

    2011-05-26 16:56:39,368 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0.GA_SOA (build: SVNTag=5.1.0.GA_SOA date=201102110032)] Started in 4m:23s:735ms
    2011-05-26 16:57:35,604 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-13) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR

    Should I pay attention to this warning?

    The second question:

    I launched a terminal window and navigate to the helloworld directory.

    When I run

    ant deploy, Quickstart_helloworld.esb build and deploy successfully.

    But when I run ant runtest, this build failed.

    The terminal window of running ant runtest shows:

    C:\Users\Administratorcd c:\jboss-soa-p-5\jboss-as\samples\quickstarts\helloworld
    c:\jboss-soa-p-5\jboss-as\samples\quickstarts\helloworldant runtestBuildfile: c:\jboss-soa-p-5\jboss-as\samples\quickstarts\helloworld\build.xml
    check-jbossesb-dist:
    qslib-dependencies:
    non-qslib-dependencies:
    jbossesb-quickstart-override:
    jbossesb-source-dependencies:
    jbossesb-server-dependencies: [echo] Using profile: default
    check-as-version: [echo] c:\jboss-soa-p-5\jboss-as\server\default
    jbossesb-dependencies-as4:
    jbossesb-dependencies-as5:
    messaging-config:
    messaging-dependencies:
    jbossmq-dependencies:
    hornetq-dependencies:
    quickstart-specific-dependencies:
    classpath-dependencies-as4:
    classpath-dependencies-as5:
    quickstart-specific-checks:
    dependencies:
    compile: [javac] c:\jboss-soa-p-5\jboss-as\samples\quickstarts\conf\base-build.xml:437: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] c:\jboss-soa-p-5\jboss-as\samples\quickstarts\conf\base-build.xml:442: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
    runtest: [echo] Runs Test JMS Sender [java] Exception in thread "main" javax.naming.NameNotFoundException: ConnectionFactory not bound [java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
    [java] at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
    [java] at org.jnp.server.NamingServer.getObject(NamingServer.java:785) [java] at org.jnp.server.NamingServer.lookup(NamingServer.java:443) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) [java] at sun.rmi.transport.Transport$1.run(Transport.java:159) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at sun.rmi.transport.Transport.serviceCall(Transport.java:155) [java] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) [java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) [java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [java] at java.lang.Thread.run(Thread.java:619) [java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255) [java] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233) [java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142) [java] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) [java] at javax.naming.InitialContext.lookup(InitialContext.java:392) [java] at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage.setupConnection(SendJMSMessage.java:52) [java] at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage.main(SendJMSMessage.java:81)
    BUILD FAILEDc:\jboss-soa-p-5\jboss-as\samples\quickstarts\helloworld\build.xml:14: Java returned: 1
    Total time: 18 secondsc:\jboss-soa-p-5\jboss-as\samples\quickstarts\helloworld

    The server console shows:

    2011-05-26 17:16:38,008 WARN [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner) Failed to process changesorg.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
    DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_esb,service=Queue" is missing the following dependencies: Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured") Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured") Deployment "jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_gw,service=Queue" is missing the following dependencies: Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured") Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured") Deployment "jboss.esb.vfszip:/C:/jboss-soa-p-5/jboss-as/server/default/deploy/Quickstart_helloworld.esb/" is missing the following dependencies: Dependency "UNKNOWN jboss.esb.vfszip:/C:/jboss-soa-p-5/jboss-as/server/default/deploy/Quickstart_helloworld.esb/" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_esb,service=Queue' **") Dependency "UNKNOWN jboss.esb.vfszip:/C:/jboss-soa-p-5/jboss-as/server/default/deploy/Quickstart_helloworld.esb/" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.esb:deployment=jbossesb.esb' **") Dependency "UNKNOWN jboss.esb.vfszip:/C:/jboss-soa-p-5/jboss-as/server/default/deploy/Quickstart_helloworld.esb/" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_gw,service=Queue' **")
    DEPLOYMENTS IN ERROR: Deployment "jboss.messaging:service=ServerPeer" is in error due to the following reason(s): Configured Deployment "UNKNOWN jboss.esb.vfszip:/C:/jboss-soa-p-5/jboss-as/server/default/deploy/Quickstart_helloworld.esb/" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_gw,service=Queue' **, ** UNRESOLVED Demands 'jboss.esb.quickstart.destination:name=quickstart_helloworld_Request_esb,service=Queue' **, ** UNRESOLVED Demands 'jboss.esb:deployment=jbossesb.esb' ** Deployment "jboss.messaging:service=PostOffice" is in error due to the following reason(s): Configured
    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1008) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:954) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)

    Can some body provide expert comments for me?

    Thanks.

    DB:3.09:Build Failed About Jboss Esb Sample Quickstarts Helloworld 1z


    One more question:

    I am confused why the server will create almost a handard links with Sybase,

    and these links are in AWAITING_COMMAND status and seem to be not active.

    Can the number of links from the database server be configured somewhere?

    Thanks.

  • RELEVANCY SCORE 3.07

    DB:3.07:Bad Class File : Jbossesb-Rosetta.Jar(Org/Jboss/Soa/Esb/Acti a9



    I have downloaded the jboss-4.2.1.GA.zip for App server and jbossesb-4.2.1GA.zip for ESB. I have configured the ESB with the app server.When i am trying to deploy the helloworld (samples\quickstarts\helloworld) using the ant deploy getting the following error message.compile: [javac] Compiling 3 source files to E:\jbossesb-4.2.1GA\samples\quickstarts\helloworld\build\classes [javac] E:\jbossesb-4.2.1GA\samples\quickstarts\helloworld\src\org\jboss\soa\esb\samples\quickstart\helloworld\MyJMSListenerAction.java:23: cannot access org.jboss.soa.esb.actions.AbstractActionLifecycle [javac] bad class file: E:\jbossesb-4.2.1GA\lib\jbossesb.sar\lib\jbossesb-rosetta.jar(org/jboss/soa/esb/actions/AbstractActionLifecycle.class) [javac] class file has wrong version 49.0, should be 48.0 [javac] Please remove or make sure it appears in the correct subdirectory of the classpath. [javac] import org.jboss.soa.esb.actions.AbstractActionLifecycle; [javac] ^ [javac] 1 errorMy system configuration is :Window 2003 server,jdk1.5.0_06apache-ant-1.6.5I tried to resolve this by installing the jdk1.5.0_15 and ant 1.7.0, but still the problem not solved.Please let me know if any one knows the solution for this problem.thanks.

    DB:3.07:Bad Class File : Jbossesb-Rosetta.Jar(Org/Jboss/Soa/Esb/Acti a9


    Thank you Daniel.Problem is solved. In the classpath Jdk1.4.2 \lib folder is appended. I removed lib folder from classpath and working fine.Sree

  • RELEVANCY SCORE 3.06

    DB:3.06:Jboss Esb Server With Eclipse Galileo (3.5) z8



    I have downloaded the JBoss ESB Server.I intend to use the JBoss ESB as a standalone system (without the JBoss AS).I believe thats what the JBoss ESB Server is meant for.However, the sample I have seen is for the JBoss ESB/JBoss AS using Eclipse plugins.I'd like to use an Eclipse Plugin with the JBoss ESB Server version.I'd appreciate any pointers.regards.

    DB:3.06:Jboss Esb Server With Eclipse Galileo (3.5) z8


    I have downloaded the JBoss ESB Server.I intend to use the JBoss ESB as a standalone system (without the JBoss AS).I believe thats what the JBoss ESB Server is meant for.However, the sample I have seen is for the JBoss ESB/JBoss AS using Eclipse plugins.I'd like to use an Eclipse Plugin with the JBoss ESB Server version.I'd appreciate any pointers.regards.

  • RELEVANCY SCORE 3.06

    DB:3.06:Packaging Deployment Options? za



    Hi,

    I was wondering what were the different deployment options available to pass from an ESB project in JBoss Developper and a standalone installation of JBoss SOA Plateform. I've been looking around for a while and didn't find a clear step-by-step description in the documentation. Here is what I found/tested:

    1) Export my ESB project as an ".esb" file and deploy it through hot deployment or through the administrative console. In both cases I get the following error:

    Caused by: java.io.IOException: Invalid white space character (0xc) in text to output

    at com.ctc.wstx.sw.XmlWriter.throwInvalidChar(XmlWriter.java:545)

    at com.ctc.wstx.sw.BufferingXmlWriter.writeAttrValue(BufferingXmlWriter.java:1058)

    at com.ctc.wstx.sw.BufferingXmlWriter.writeAttribute(BufferingXmlWriter.java:891)

    at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:483)

    == Do you have an idea of what could be wrong?

    2) Scripting deployments such as what is presented in the quickstarts section, but these scripts are specific to quickstarts (with specific targets).

    == Are there officials base build ant scripts (compile, package, deploy, etc...) to consider or do I have to go from these quickstarts scripts to create my owns?

    == Same question with maven: are there specific maven plugin or goals for JBoss ESB?

    Thank you very much in advance for your support,

    Regards,

    Seb!

    DB:3.06:Packaging Deployment Options? za


    Seb, do you have a small test case case which demonstrates this? Do you see the same problem if you copy the .esb in by hand (vs. deploy through the admin console)?

    In terms of base ant scripts, you could either use the quickstart scripts or do your own. In terms of maven support, this article is pretty good :

    http://community.jboss.org/wiki/JBossESBTrailblazerbuildingwithMaven2

  • RELEVANCY SCORE 3.05

    DB:3.05:How To Run The Jboss Esb Quickstarts Helloworld Client From Command Line(Linux Terminal) Without Using Ant? f9



    I am able to deploy Quickstart_helloworld.esb and then test it using "ant runtest" successfully.

    Now i need to do the same test using commands like below in terminal along with required jars:

    ToCompile:

    javac SendJMSMessage.java

    ToRun:

    java SendJMSMessage

    Note: i understand, the command "ant runtest" in this particular example is invoking "org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage" java class.

    Can some body suggest me, the order/list of supporting jars i need to include in the command line

    when running below commands:

    javac SendJMSMessage.java

    java -cp listofjars SendJMSMessage

    Thanks in Advance.

    DB:3.05:How To Run The Jboss Esb Quickstarts Helloworld Client From Command Line(Linux Terminal) Without Using Ant? f9


    You might have better luck determining the list for "ant sendesb", which I believe would be the same list as the ServiceInvoker (see this thread https://community.jboss.org/thread/144658?start=0tstart=0).

    The "exec-classpath" classpath that the runtest target uses may bring in a lot of stuff that you wouldn't necessarily need for sending a JMS message, but that might be required for other quickstarts. I'd start with just the messaging JARs that are in the exec-classpath, and then expand out when classes are not found by searching for what JAR that class is in and then adding it to the path.