[Beginner's Corner] - Migrating from jboss 4.2.3 to 5.1.0
by gajendra jangid
gajendra jangid [https://community.jboss.org/people/gjangid] created the discussion
"Migrating from jboss 4.2.3 to 5.1.0"
To view the discussion, visit: https://community.jboss.org/message/749815#749815
--------------------------------------------------------------
Hi,
I am migrating from jboss 4.2.3 to 5.1.0 and after deploying my application and placing -ds.xml (xauthority-jms-ds.xml) file.
I have removed hsqldb-ds.xml from server/deploy folder and hsqldb-persistence-service.xml from server/deploy/messaging folder.
I am facing folloeing error.Please suggest me any solution.
Here are the error logs and xauthority-jms-ds.xml :-
03:44:21,785 [main] ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "JBossTimerServiceFactory" is missing the following dependencies:
Dependency "jboss.ejb:service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.ejb:service=EJBTimerService" is missing the following dependencies:
Dependency "jboss.ejb:persistencePolicy=database,service=EJBTimerService" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.ejb:persistencePolicy=database,service=EJBTimerService' **")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" is missing the following dependencies:
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView' **")
Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint" is missing the following dependencies:
Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
Deployment "jboss.j2ee:module="AsyncRegistrationBean.jar",service=EjbModule" is missing the following dependencies:
Dependency "jboss.ejb:service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.j2ee:module="common-utils-mdbs1.jar",service=EjbModule" is missing the following dependencies:
Dependency "jboss.ejb:service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=ConnectionFactoryBinding" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=TxCM" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=ManagedConnectionPool" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionFactory" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.jca:name=JmsXA,service=TxCM" is missing the following dependencies:
Dependency "jboss.jca:name=JmsXA,service=ManagedConnectionPool" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" 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 "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" 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 "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **")
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.messaging:service=ServerPeer" is missing the following dependencies:
Dependency "jboss.messaging:service=JMSUserManager" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.messaging:service=JMSUserManager' **")
Deployment "jboss.mq.destination:name=AsynchXpdlMessageDrivenBean,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=BulkProvisionParserQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=BulkProvisionQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=BulkUserImportQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=CacheNotificationsTopic,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=INVJVTEventTopic,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=JVTEventTopic,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=JawaQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=JawaTestResponse,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=JawaTopic,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=MessageQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=MessagingRequestQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=MessagingResponseQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=OMJVTEventTopic,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=OMMessageQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=OMResponseMessageQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=OMXVTEventTopic,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=OMXVTReplyTopic,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=OmegaQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=OmegaRelayMDB,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=OrderQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=ResponseMessageQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=TestMessagingRequestQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=TestMessagingResponseQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=UnregisterQueue,service=Queue" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq.destination:name=XVTEventTopic,service=Topic" is missing the following dependencies:
Dependency "jboss.mq:service=DestinationManager" (should be in state "Create", but is actually in state "Configured")
Deployment "jboss.mq:service=DestinationManager" is missing the following dependencies:
Dependency "jboss.messaging:service=ServerPeer" (should be in state "Create", but is actually in state "Configured")
DEPLOYMENTS IN ERROR:
Deployment "jboss.ejb:persistencePolicy=database,service=EJBTimerService" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.ejb:persistencePolicy=database,service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **, ** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView' **
Deployment "jboss.messaging:service=JMSUserManager" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.messaging:service=JMSUserManager' **
Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
Deployment "jboss.messaging:service=PostOffice" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.messaging:service=PostOffice' **
03:44:21,795 [main] INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
03:44:21,822 [main] INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
03:44:21,842 [main] INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 49s:13ms
And i have attached xauthority-jms-ds.xml
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/749815#749815]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 8 months
[JBoss Tools] - Add jboss-deployment-structure.xml dependencies to Eclipse build path.
by Bron Eubanks
Bron Eubanks [https://community.jboss.org/people/beubanks] created the discussion
"Add jboss-deployment-structure.xml dependencies to Eclipse build path."
To view the discussion, visit: https://community.jboss.org/message/751024#751024
--------------------------------------------------------------
Background: I am deploying a dynamic web project to JBoss AS 7.1.1 using Eclipse 4.2 with JBoss Tools 3.3.0 Final. My project's build path includes the JRE System Library, JBoss 7.1 Runtime, and Web App Libraries (the WEB-INF/lib folder). I also have a jboss-deployment-structure.xml file that defines additional module dependencies such as the following:
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.slf4j" />
<module name="org.apache.log4j" />
</dependencies>
</deployment>
</jboss-deployment-structure>
The problem is, the slf4j and log4j modules are not included in the project's build path. While the server resolves them correctly at runtime because of the jboss-deployment-structure.xml file, Eclipse doesn't include them. So the following declaration in the Java code would result in a build error because org.apache.log4j cannot be resolved to a type:
private static final org.apache.log4j.Logger log = org.apache.log4j.Logger.getLogger(Example.class);
The JBoss runtime that the project is using is configured correctly. It points to a valid JBoss directory, and the module dependencies are properly installed in the server.
So, is there a way to *automatically* add the jboss-deployment-structure module dependencies to the Eclipse build path? So far, I've been unable to find a way to do this.
I have found a few workarounds, but none of them are ideal, and they seem to completely miss the point of module-based dependencies:
1. Customize the Default Classpath Entries for the server runtime. This is not acceptable because it must be done in each developer's workspace – and possibly per project since projects may have different, conflicting dependencies.
2. Add the libraries to WEB-INF/lib. This is not acceptable because it defeats the purpose of server modules.
3. Add the libraries to a user library for the project. This could work, but it's very inconvenient, because each developer on the team would have to add the jars to the user libraries in their workspaces.
Have I missed a solution to this problem that JBoss Tools already provides? Or, does anyone have any other ideas?
Thanks in advance,
Bron
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/751024#751024]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 8 months
[jBPM] - How to list human tasks with HQ API?
by Alex Wulms
Alex Wulms [https://community.jboss.org/people/awulms_work] created the discussion
"How to list human tasks with HQ API?"
To view the discussion, visit: https://community.jboss.org/message/751019#751019
--------------------------------------------------------------
Hi,
I have created a human task using the "human task view" plugin in eclipse. The task is made for the user "krisv". It shows-up both in the "human task view" in eclipse and in the jbpm console when I login with krisv user (based on the demo/evaluation set-up of jBPM 5.3). The task is in status reserved.
I have now made a small java program that connects to the human task service on localhost on port 5445. The program is supposed to get all reserved tasks for krisv user but it returns 0 results.
Here is the code that I use:
public static void main(String args[])
{
String user="krisv";
String language="en-UK";
List<Status> status = Arrays.asList(new Status[] { Status.Reserved });
System.out.println("*** Connecting to human task client with HornetQ protocol");
SyncTaskServiceWrapper tk = new SyncTaskServiceWrapper(new AsyncHornetQTaskClient());
tk.connect("127.0.0.1", 5445);
System.out.println("*** Getting " + status + " tasks for " + user + " with language " + language);
List<TaskSummary> tasks = tk.getTasksAssignedAsPotentialOwnerByStatus(user, status, language);
tasks.addAll(tk.getTasksOwned(user, status, language));
System.out.println("*** Got " + tasks.size() + " tasks");
}
It shows at the end "got 0 tasks"
Any idea what I'm doing wrong?
Any help is appreciated.
Thanks and kind regards,
Alex
PS: Can you kindly add jBPM 5.3 to the list of "Categories" in this forum?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/751019#751019]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 8 months
[jBPM] - processinstanceinfo blob field is not getting updated with up to date processinstance information at save point.
by malabalu
malabalu [https://community.jboss.org/people/malabalu] created the discussion
"processinstanceinfo blob field is not getting updated with up to date processinstance information at save point."
To view the discussion, visit: https://community.jboss.org/message/751080#751080
--------------------------------------------------------------
We are using jbpm5.2 with open jpa. When we start the process, it is adding the processinstance to the processinstanceinfo and store the lob with state as inactive. In jbpm code, the process is getting set active after the internalstart of the process and then it executes 2 of the nodes and waiting for external event. But when the transaction commits, I see only the initial data getting stored into db with state inactive and so for the signal event, it is reconstructing the process with state inactive and nothing happens.
my questions are:
how do I make sure the processinstanceinfo blob is having up to date info on the process until the save point when the transaction commits and wait for external signal.
when I look at the update() method on processinstanceinfo class, it is having preUpdate() annotation but it doesnt appear to work otherwise the blob should have been updated as expected.
also in jbpm, after the internal start, the processinstance variable is getting updated which is declared as transient in processinstanceinfo class.Is this the problem that it is not updating the processinstanceinfo entity before it persist to the db.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/751080#751080]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 8 months