[JBoss Messaging] - Error in Messaging
by Mallikharjuna Areti
Mallikharjuna Areti [https://community.jboss.org/people/malli002] created the discussion
"Error in Messaging"
To view the discussion, visit: https://community.jboss.org/message/787273#787273
--------------------------------------------------------------
Hi All,
I am getting below error in one of our JBOSS server (version 5.1.*)
08:40:52,636 ERROR [AbstractKernelController] Error installing to Configured: name=jboss.messaging:service=ServerPeer state=Instantiated mode=Manual requiredState=Configured
* org.jboss.deployment.DeploymentException: Error configuring attribute ServerPeerID
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:52)
at org.jboss.system.metadata.ServiceAttributeMetaData.getValue(ServiceAttributeMetaData.java:155)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:151)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:114)
at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)
at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.install(ServiceController.java:274)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:90)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:470)
at java.lang.Integer.valueOf(Integer.java:554)
at sun.beans.editors.IntEditor.setAsText(IntEditor.java:21)
at org.jboss.system.metadata.ServiceTextValueMetaData.getValue(ServiceTextValueMetaData.java:132)
at org.jboss.system.metadata.ServiceAttributeMetaData.getValue(ServiceAttributeMetaData.java:151)
... 52 more
08:40:52,641 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/apps_01/webapps/JBoss/conf/server0/deploy/messaging/messaging-service.xml state=PreReal mode=Manual requiredState=Real
Any body have idea about this error and any work around.
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/787273#787273]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months
[jBPM] - jBPM REST API for custom client application
by Justin Robbins
Justin Robbins [https://community.jboss.org/people/jhrobbin] created the discussion
"jBPM REST API for custom client application"
To view the discussion, visit: https://community.jboss.org/message/734916#734916
--------------------------------------------------------------
Hi folks,
I'd appreciate some suggestions on the topic of exposing jBPM REST API to a custom client application.
Cliff Notes:
Bulding a custom smartphone app (not just using BPM Console client). Better to re-use the REST API already exposed by the Console-Server or roll our own REST API for jBPM? (See details below for better explanation)
Details:
Let's say we want to build a smartphone app that provides a small subset of what the BPM Console browser app does along with some other functionality specific to our own application. To be clear, the smartphone app doesn't just interact with jBPM. If that were the case, then I assume it would be a no-brainer to have the smartphone app directly hit the Console-Server.
I'm thinking the smartphone app makes REST calls to our own server API. From there, one option would be for our server API to make REST API calls to the Console-Server (also running in our server environment) for jBPM related things like get a list of tasks, claim a task, etc.
Would that be preferrable to rolling our own? Or would it be better to skip using the Console-Server and have our API server side code use the jBPM Java API instead. I'm assuming I can do things like get a list of tasks for a user, claim a test, etc using the jBPM Java API (I haven't dug deep into the capabilities of the jBPM Java API). I have seen the list of available URIs prvided by the Console-Server so I think I have a handle on what the Console-Server API exposes.
Many thanks for your input.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/734916#734916]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months
[jBPM] - Re: Help using persistence with JBPM 5.4
by doboss
doboss [https://community.jboss.org/people/doboss] created the discussion
"Re: Help using persistence with JBPM 5.4"
To view the discussion, visit: https://community.jboss.org/message/787148#787148
--------------------------------------------------------------
Okay, I got it working by changing the code like this:
@PersistenceUnit(unitName = "org.jbpm.persistence.jpa")
private EntityManagerFactory emf;
public void runIt()
{
try
{
if (kbase == null)
{
// load up the knowledge base
kbase = readKnowledgeBase();
}
Environment env = KnowledgeBaseFactory.newEnvironment();
env.set(EnvironmentName.ENTITY_MANAGER_FACTORY, emf);
// create a new knowledge session that uses JPA to store the runtime
// state
StatefulKnowledgeSession ksession = JPAKnowledgeService.newStatefulKnowledgeSession(kbase, null, env);
int sessionId = ksession.getId();
JPAWorkingMemoryDbLogger logger = new JPAWorkingMemoryDbLogger(ksession);
If anyone wants more details, I would be happy to provide them.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/787148#787148]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months
[IronJacamar] - trouble with RAR with ResourceAdapter
by Frank Langelage
Frank Langelage [https://community.jboss.org/people/lafr] created the discussion
"trouble with RAR with ResourceAdapter"
To view the discussion, visit: https://community.jboss.org/message/779991#779991
--------------------------------------------------------------
I have a rar file in charge for some month on JBoss AS7 Alpha1-SNAPSHOT, using ironjacamer 1.0.13.Final now.
After some trouble with the migration from 4.2x it worked fine for a long time. Code was not changed.
Now I encounter problems again.
Validation is still successful:
ksh validator.sh $JBOSS_HOME/standalone/deployments/filesystem.rar
Validation sucessful
standalone.xml contains:
| | <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"> |
| | <resource-adapters> |
| | <resource-adapter> |
| | <archive>filesystem.rar</archive> |
| | <config-property name="Path">/mbi</config-property> |
| | <connection-definitions> |
| | <connection-definition jndi-name="java:/Filesystem" class-name="biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory"/> |
| | </connection-definitions> |
| | </resource-adapter> |
| | </resource-adapters> |
| | </subsystem> |
Sources are:
FilesystemConnectionFactoryImpl.java
FilesystemConnectionImpl.java
FilesystemConnectionManager.java
FilesystemManagedConnection.java
FilesystemManagedConnectionFactory.java
FilesystemManagedConnectionMetaData.java
FilesystemResourceAdapter.java
ci/FilesystemConnectionFactory.java
ci/FilesystemConnection.java
>From server.log:
22:25:20,347 INFO [org.jboss.as.server.deployment.scanner#startScanner] JBAS015012: Started FileSystemDeploymentService for directory /mbi/tools/jboss/7.2/standalone/deployments
22:25:20,356 INFO [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "filesystem.rar"
22:25:48,109 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#<init>]
22:25:48,111 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#<init>]
22:25:48,112 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#setLogWriter] java.io.PrintWriter@1ee88dd
22:25:48,112 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#setLogWriter]
22:25:48,113 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#createConnectionFactory]
22:25:48,114 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#createConnectionFactory] biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionFactoryImpl@15b9f9a
22:25:48,115 INFO [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/Filesystem
22:25:48,119 INFO [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/mbi/tools/jboss/7.2/standalone/tmp/vfs/tempf60d0c19e890fd72/filesystem.rar-dafe9e7274262254/contents/
22:25:53,058 INFO [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/Filesystem]
...
22:30:03,300 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#hashCode]
22:30:03,304 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#hashCode] 17
22:30:03,306 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionImpl#<init>] biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory@11
22:30:03,307 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionImpl#<init>]
22:30:03,309 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionImpl#getRepositoryPath]
22:30:03,311 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#getResourceAdapter]
22:30:03,312 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#getResourceAdapter] null
22:30:03,314 ERROR [biz.mbisoftware.fn.jca.filesystem.FilesystemConnectionImpl#getRepositoryPath] this.mcf.getResourceAdapter() == null
22:30:03,315 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#getResourceAdapter]
22:30:03,317 DEBUG [biz.mbisoftware.fn.jca.filesystem.FilesystemManagedConnectionFactory#getResourceAdapter] null
No instance of FilesystemResourceAdapter taking the "Path" property is created and set for the ManagedConnectionFactory object during deployment.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/779991#779991]
Start a new discussion in IronJacamar at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months