[EJB3] - Runtime Exception while creating EJB Object
by Hushen Savani
Hushen Savani [https://community.jboss.org/people/hushen.savani] created the discussion
"Runtime Exception while creating EJB Object"
To view the discussion, visit: https://community.jboss.org/message/648806#648806
--------------------------------------------------------------
Hi Community,
I have developed an application with *Java 1.6*, *EJB-2.1*. The application is deployed on *JBossAS-5.1.0*. The application has been running very smooth for long a time. But for last two days, I found following sort of Runtime Exception while creating EJB Local Object/Local Home:
*Log Snippet-1*:
2012-01-25 17:09:02,896 ERROR [STDERR] (WorkerThread#4[127.0.0.1:47153])
Caused by: java.lang.NullPointerException
2012-01-25 17:09:02,896 ERROR [STDERR] (WorkerThread#4[127.0.0.1:47153])
at
org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyF
actory.java:343)
2012-01-25 17:09:02,896 ERROR [STDERR] (WorkerThread#4[127.0.0.1:47153])
at
org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:133)
2012-01-25 17:09:02,896 ERROR [STDERR] (WorkerThread#4[127.0.0.1:47153])
at $Proxy257.create(Unknown Source)
*Log Snippet-2*:
java.lang.NullPointerException
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:457)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy263.getDynamicLoopMessage_Generalized(Unknown Source)
*Log Snippet-3*:
2012-01-17 16:44:49,063 ERROR [org.jboss.ejb.plugins.LogInterceptor] (WorkerThread#5[192.168.1.76:19743]) RuntimeException in method: public abstract com.elitecore.billingengine.utils.BEResultObject com.elitecore.billingengine.ejb.billpreview.interfaces.IBillPreviewSessionLocal.doBasePriceCalculation(com.elitecore.billingengine.utils.BEHashMap):
java.lang.NullPointerException
at com.elitecore.billingengine.ejb.billpreview.sessionfacade.BillPreviewSessionFacade.doBasePriceCalculation(BillPreviewSessionFacade.java:357)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Also, the whole server.log is attached with this thread. Pls. suggest some pointers on the same.
Thank you.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/648806#648806]
Start a new discussion in EJB3 at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 4 months
[jBPM] - Re: Console crashes on opening Process Overview (fresh jBPM5.2 installation)
by hamsterdancer
hamsterdancer [https://community.jboss.org/people/hamsterdancer] created the discussion
"Re: Console crashes on opening Process Overview (fresh jBPM5.2 installation)"
To view the discussion, visit: https://community.jboss.org/message/647034#647034
--------------------------------------------------------------
Ok we found the problem.
As Tihomir already said, the problem is about the version of commons codec. We found THREE different versions of commons codec in the different projects which are parts of the jBPM Installer. 1.3, 1.4 and 1.5.
It looks like jboss loads the libraries in a different order on different systems. The following output (I've got by a colleague) may help to fix the problem permanently.
> 18:32:21,749 INFO [stdout] (http-localhost-127.0.0.1-8080-1)
> >>>>>>>>>>>> commons codec location :
> vfs:/content/jbpm-gwt-console-server.war/WEB-INF/lib/org.apache.commons.codec_1.3.0.v201101211617.jar
> 18:32:21,750 ERROR
> [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gwt-console-server]]
> (http-localhost-127.0.0.1-8080-1) StandardWrapper.Throwable:
> java.lang.NoSuchMethodError:
> org.apache.commons.codec.binary.Base64.encodeBase64String([B)Ljava/lang/String;
Our temporary solution is to change the build.xml to exclude the old library on the jboss installation
> <!-- Install reporting AS7 -->
> <target name="install.reporting.into.jboss7" depends="check.birt.as7" if="birt.download" >
> <mkdir dir="${install.home}/birt"/>
> <unzip src="${install.home}/lib/birt-runtime-${birt.version.as7}.zip"
> dest="${install.home}/birt"/>
> <copy todir="${install.home}/target/jbpm-gwt-console-server-war/WEB-INF/lib">
> <fileset dir="${install.home}/birt/birt-runtime-${birt.version.as7}/ReportEngine/lib">
> <include name="**/*.jar"/>
> <exclude name="**/org.apache.commons.codec_1.3.0.v201101211617.jar"/>
> </fileset>
> </copy>
I hope it helps without causing additional problems^^
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/647034#647034]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 6 months
[jBPM] - Re: jBPM processes started from Java code dont show up in jBPM process console
by Maïté Braud
Maïté Braud [https://community.jboss.org/people/mbraud] created the discussion
"Re: jBPM processes started from Java code dont show up in jBPM process console"
To view the discussion, visit: https://community.jboss.org/message/646856#646856
--------------------------------------------------------------
Hi
I've got a similar issue except that in my case, processes started from java simply reset entries in my database.
I have only one process available. The first step in this process is a human task.
If I start 2 process instances from the jBPM console, both process instances appear in the "Process Overview" tab and they also appear in the database (I'm persisting PROCESSINSTANCEINFO, PROCESSINSTANCELOG, SESSIONINFO, VARIABLEINSTANCELOG, WORKITEMINFO and NODEINSTANCELOG in a H2 DB).
If I start the same process from the java code, my 2 previous process instances disappear (both from the console and the database which is consistent) and get replaced by the new process instance.
If I start another process instance from the java code, it replaces the previous one so that I can never have more than 2 process instances started from my java code.
Here is my java code:
EntityManagerFactory emf = Persistence.createEntityManagerFactory( "org.jbpm.persistence.jpa" );
Environment env = KnowledgeBaseFactory.newEnvironment();
env.set(EnvironmentName.ENTITY_MANAGER_FACTORY, emf);
env.set(EnvironmentName.TRANSACTION_MANAGER, TransactionManagerServices.getTransactionManager());
env.set( EnvironmentName.GLOBALS, new MapGlobalResolver() );
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(ResourceFactory.newClassPathResource(ACCESS_WORKFLOW_FILE), ResourceType.BPMN2 );
KnowledgeBase kbase = kbuilder.newKnowledgeBase();
StatefulKnowledgeSession ksession = JPAKnowledgeService.newStatefulKnowledgeSession(kbase, null, env);
JPAWorkingMemoryDbLogger dbLogger = new JPAWorkingMemoryDbLogger(ksession);
KnowledgeRuntimeLogger logger = KnowledgeRuntimeLoggerFactory.newFileLogger(ksession, "test");
ksession.getWorkItemManager().registerWorkItemHandler("Human Task", new CommandBasedWSHumanTaskHandler(ksession));
ksession.startProcess(ACCESS_WORKFLOW_ID, new HashMap());
dbLogger.dispose();
logger.close();
Also I forgot to mention it but I'm deploying jBPM 5.1 on Tomcat 6 and I'm not using Guvnor but simply a directory specified in "-Djbpm.console.directory".
I've also noted some strange behaviour where my process instances also seem to be reset everytime I restart tomcat. The entries remain in the DB after I shutdown Tomcat and they also remain in it once I've restarted Tomcat and logged in the jBPM console again but the moment I go to the "Process Overview" tab and jBPM reloads the process definition, all process instances disappear from my DB.
I think that I'm missing something important here but I don't know what.
Any help would be greatly appreciated
Maïté
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/646856#646856]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[jBPM] - New Installation of jBPM 5 using Existing Installation of JBoss 7 and Eclipse Indigo
by Patty Eilers
Patty Eilers [https://community.jboss.org/people/peilers64] created the discussion
"New Installation of jBPM 5 using Existing Installation of JBoss 7 and Eclipse Indigo"
To view the discussion, visit: https://community.jboss.org/message/649774#649774
--------------------------------------------------------------
I am trying to install jBPM 5 using my existing installations for JBoss7 and Eclipse Indigo. I have modified the build.properties file to point at my existing Eclipse installation and removed all mention of JBoss5.
In the installation documentation for jBPM the following instructions are presented:
h3. Installing
In the install dir, run installation script:
+ant install.guvnor.into.jboss+
+ant install.designer.into.jboss+
+ant install.jBPM-gwt-console.into.jboss+
+ant install.jBPM-eclipse.into.eclipse+
+ant install.drools-eclipse.into.eclipse+
The problem is that the last two tasks do not exist in the build.xml file. I have found a task called +install.droolsjbpm-eclipse.into.eclipse+ and another called +install.jBPM.runtime.+ I have run them both, as well as +install.demo.eclipse,+ but still neither the Guvnor or Console are accessible.
It would be great if someone could update the jBPM5 installer documentation. It seems that most people would already have both JBoss and Eclipse installed independently before they choose to install jBPM5. I have tried every flavor of JBPM5 installation--full/comprehensive and pieces parts--but I remain unsuccessful in getting access to the Guvnor and Console.
Ready to give up entirely on jBPM and head over to take a look at Intalio....
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/649774#649774]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[JBoss Tools] - Runtime Environment 7.1 Default Config 3.3M5
by Mark Rosenthal
Mark Rosenthal [https://community.jboss.org/people/mwr0707] created the discussion
"Runtime Environment 7.1 Default Config 3.3M5"
To view the discussion, visit: https://community.jboss.org/message/647007#647007
--------------------------------------------------------------
On 3.3M5, I've created a 7.1 runtime env and set the JRE to a Java 1.6 installation.
When creating a new Dynamic Web Project, the project configuration "Default JBoss 7.1 runtime configuration" insists on configuring a non-existent (in my case) 1.7 JRE by default.
The symptoms are deployable class files built at 1.7 which fail at deployment when a 1.7 JRE is not present.
This can be worked around by modifying the default configuration during project creation. After project creation, this can be worked around by changing the project Java Facet and Compiler Compliance Level.
The desired behavior is for the "Default JBoss 7.1 runtime configuration" during project creation to utilize the setting in the configured JBoss 7.1 Server runtime by default.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/647007#647007]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 8 months
[jBPM] - Handling Faults leads to log entry: cvc-id.2: There are multiple occurrences of ID value 'TestException'.
by sebb
sebb [https://community.jboss.org/people/sebb] created the discussion
"Handling Faults leads to log entry: cvc-id.2: There are multiple occurrences of ID value 'TestException'."
To view the discussion, visit: https://community.jboss.org/message/648364#648364
--------------------------------------------------------------
While trying to figure how to deal with exceptions I found the way by "catching" Error Events with a Signal. In order to be able to catch an Error Event I have to do the following things:
1. Add the metadata key "ErrorEvent" with value "FaultName" of my ErrorEvent (in my case: ErrorEvent:TestException).
2. Define the EventType of the Signal with a combination of "Error-[node id of subprocess]-[FaultName of my ErrorEvent]" (in my case: Error-_6-TestException).
But as soon as I do this the log shows the following entries:
(null: 19, 61): cvc-id.2: There are multiple occurrences of ID value 'TestException'.
(null: 19, 61): cvc-attribute.3: The value 'TestException' of attribute 'id' on element 'error' is not valid with respect to its type, 'ID'.
I dont even understand those entries. Of course I will have multiple occurences of the same ID if I reference to it inside my process.
Any opinions to that problem?
Thanks :)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/648364#648364]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 8 months