[Installation, Configuration & DEPLOYMENT] - Re: Deployment functionality of JBoss AS 4.2.1.GA refuses to
by PeterJ
This sure looks like some UAC weirdness, but that is usually limited to the Program Files and windows folders, and usually only shows up if you use different accounts to access the data.
Could you post the contents of testShop-ds.xml? It's size is really small.
Also, post the results of "jar -tf testShop-ear.ear"
anonymous wrote : I already had that problem before but it disappeared after a time...
I had a problem at one time that would suddenly disappear and then also mysteriously reappear. In my case, a build script from a co-worker placed a stray JAR file in the JDK's endorsed directory. The problem would then go away when I installed a new JDK, and of course reappear after I ran that build script. I found the problem by adding "-verbose:class" to the java command line and looking for classes loaded from stray locations. Then I had a few choice words with my co-worker who was too lazy to set a classpath in various locations in his build script.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234162#4234162
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234162
14 years, 11 months
[Persistence, JBoss/CMP, Hibernate, Database] - persistence.xml in ear entities in lib/lib1/jar => 'could no
by smolin
Hello,
I try to get such ear:
ear
|->ejb1.jar
|->ejb2.jar
|-lib
|-lib1.jar
|-META-INF
|->persistence.xml
lib1.jar contains JPA entities (classes annotated by @Entity)
persistence.xml:
| <?xml version="1.0" encoding="UTF-8"?>
| <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
|
| <persistence-unit name="PU" transaction-type="JTA">
| <provider>org.hibernate.ejb.HibernatePersistence</provider>
| <jta-data-source>java:/DefaultDS</jta-data-source>
| <jar-file>lib/lib1.jar</jar-file>
| <properties>
| <property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect" />
| <property name="hibernate.hbm2ddl.auto" value="update" />
| <property name="hibernate.show_sql" value="true"/>
| </properties>
| </persistence-unit>
| </persistence>
|
I specified lib1.jar in persistence.xml: <jar-file>lib/lib1.jar</jar-file>. I also tried <jar-file>lib1.jar</jar-file> <jar-file>../lib/lib1.jar</jar-file>.
I use entities in ejb1.jar and ejb2.jar.
When deploy to JBoss 5.1.0.CR1 I get error:
| java.lang.RuntimeException: could not find relative path: lib/lib1.jar
| at org.jboss.jpa.deployment.PersistenceUnitDeployment.getRelativeURL(PersistenceUnitDeployment.java:208)
| at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:267)
| 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)
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
| at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
| at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
| at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
| at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
| at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
| at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.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.dependency.plugins.AbstractController.install(AbstractController.java:1631)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
| at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
| at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
|
What is wrong? How to solve it?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234149#4234149
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234149
14 years, 11 months
[EJB/JBoss] - Re: set TransactionTimeout during Runtime
by sams2100
Have you considered breaking up your EJB into two EJBs joined via a JMS queue? Basically have the first EJB generate the messages for the web service, and as it generates say 100 web service requests, it tosses those requests onto a queue instead of making those requests itself. Then have another EJB (MDB) consuming off of that queue and this EJB can have its own custom timeout based on when it should timeout on 100 web service requests.
This lets your first EJB reduce its work load to beat the timeout, and then the other EJB that is doing the web service requests will have its own timeout. Not only that, but since there is the second EJB doing the web requests, you can allow it do run those in parallel and get all your work done much faster and have it broken up with reasonable transaction timeouts.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234142#4234142
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234142
14 years, 11 months