aspose file tools*
The moose likes JBoss/WildFly and the fly likes JBoss persistence problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "JBoss persistence problem" Watch "JBoss persistence problem" New topic
Author

JBoss persistence problem

Adrien Ruffie
Ranch Hand

Joined: Jan 14, 2009
Posts: 90
Hello, I try to run a web app (without persistence, I don't use hibernate, EJB ...)

but when I try to deploy and run my webapp, I get the following error:


11:51:08,017 INFO [ServerImpl] Starting JBoss (Microcontainer)...
11:51:08,019 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812041714)
11:51:08,020 INFO [ServerImpl] Bootstrap URL: null
11:51:08,020 INFO [ServerImpl] Home Dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA
11:51:08,020 INFO [ServerImpl] Home URL: file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/
11:51:08,020 INFO [ServerImpl] Library URL: file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/lib/
11:51:08,021 INFO [ServerImpl] Patch URL: null
11:51:08,022 INFO [ServerImpl] Common Base URL: file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/common/
11:51:08,022 INFO [ServerImpl] Common Library URL: file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/common/lib/
11:51:08,022 INFO [ServerImpl] Server Name: default
11:51:08,022 INFO [ServerImpl] Server Base Dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA/server
11:51:08,023 INFO [ServerImpl] Server Base URL: file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/
11:51:08,023 INFO [ServerImpl] Server Config URL: file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/conf/
11:51:08,023 INFO [ServerImpl] Server Home Dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default
11:51:08,023 INFO [ServerImpl] Server Home URL: file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/
11:51:08,023 INFO [ServerImpl] Server Data Dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/data
11:51:08,023 INFO [ServerImpl] Server Library URL: file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/lib/
11:51:08,024 INFO [ServerImpl] Server Log Dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/log
11:51:08,024 INFO [ServerImpl] Server Native Dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/tmp/native
11:51:08,024 INFO [ServerImpl] Server Temp Dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/tmp
11:51:08,024 INFO [ServerImpl] Server Temp Deploy Dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/tmp/deploy
11:51:08,950 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/conf/bootstrap.xml
11:51:09,789 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.IterableTimedVFSCache]
11:51:09,800 INFO [VFSCacheFactory] Using VFSCache [IterableTimedVFSCache{lifetime=1800, resolution=60}]
11:51:10,173 INFO [CopyMechanism] VFS temp dir: /home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/tmp
11:51:10,215 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
11:51:11,481 INFO [ServerInfo] Java version: 1.6.0_16,Sun Microsystems Inc.
11:51:11,482 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 14.2-b01,Sun Microsystems Inc.
11:51:11,482 INFO [ServerInfo] OS-System: Linux 2.6.28-18-generic,i386
11:51:11,556 INFO [JMXKernel] Legacy JMX core initialized
11:51:13,879 INFO [ProfileServiceImpl] Loading profile: default from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@183d260(root=/home/aruffie/Java/Servers/jboss-5.0.0.GA/server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
11:51:13,882 INFO [ProfileImpl] Using repositoryrg.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@183d260(root=/home/aruffie/Java/Servers/jboss-5.0.0.GA/server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
11:51:13,882 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@91cf0b{key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default]}
11:51:15,630 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
11:51:23,485 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
11:51:23,486 INFO [NativeServerConfig] 3.0.4.SP1
11:51:36,813 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
11:51:37,105 INFO [MailService] Mail Service bound to java:/Mail
11:51:40,166 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
11:51:40,200 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
11:51:40,427 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
11:51:40,428 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
11:51:40,817 INFO [TransactionManagerService] Initializing recovery manager
11:51:41,189 INFO [TransactionManagerService] Recovery manager configured
11:51:41,190 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
11:51:41,225 INFO [TransactionManagerService] Starting transaction recovery manager
11:51:42,746 INFO [Http11Protocol] Initialisation de Coyote HTTP/1.1 sur http-127.0.0.1-8080
11:51:42,747 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
11:51:42,748 INFO [StandardService] D�marrage du service jboss.web
11:51:42,751 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.GA
11:51:42,844 INFO [Catalina] Server startup in 969 ms
11:51:42,872 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
11:51:44,108 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war
11:51:44,176 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
11:51:44,390 INFO [RARDeployment] Required license terms exist, view vfszip:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
11:51:44,415 INFO [RARDeployment] Required license terms exist, view vfszip:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
11:51:44,448 INFO [RARDeployment] Required license terms exist, view vfszip:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
11:51:44,499 INFO [RARDeployment] Required license terms exist, view vfszip:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
11:51:44,535 INFO [RARDeployment] Required license terms exist, view vfszip:/home/aruffie/Java/Servers/jboss-5.0.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
11:51:44,666 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
11:51:44,708 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
11:51:44,713 INFO [RAMJobStore] RAMJobStore initialized.
11:51:44,714 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
11:51:44,714 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
11:51:44,715 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
11:51:46,385 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'javaefaultDS'
11:51:46,974 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE QRTZ_JOB_DETAILS(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL, DESCRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE VARCHAR(1) NOT NULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VARCHAR(1) NOT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))
11:51:47,040 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
11:51:47,043 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
11:51:47,044 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
11:51:47,058 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
11:51:47,058 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
11:51:47,059 INFO [JobStoreCMT] JobStoreCMT initialized.
11:51:47,060 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
11:51:47,060 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
11:51:47,117 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
11:51:47,119 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
11:51:47,120 INFO [JobStoreCMT] Recovery complete.
11:51:47,120 INFO [JobStoreCMT] Removed 0 'complete' triggers.
11:51:47,120 INFO [JobStoreCMT] Removed 0 stale fired job entries.
11:51:47,126 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
11:51:47,426 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
11:51:47,550 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
11:51:47,551 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
11:51:47,662 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
11:51:47,663 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1c9c4e2 started
11:51:47,664 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
11:51:47,664 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1f43358 started
11:51:47,668 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
11:51:47,668 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1d09296 started
11:51:47,688 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
11:51:47,690 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
11:51:47,868 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
11:51:47,909 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
11:51:47,979 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
11:51:48,210 INFO [TomcatDeployment] deploy, ctxPath=/opensuit-sample-livetour, vfsUrl=opensuit-sample-livetour.war
11:51:48,460 INFO [STDOUT] [xmlmap://org.ow2.opensuit.xml.base/v1.0] INFO: Use Mapping Method 'org.ow2.opensuit.xmlmap.BindWithAnnotations'
11:51:49,034 INFO [STDOUT] [xmlmap://org.ow2.opensuit.xml.chart/v1.0] INFO: Use Mapping Method 'org.ow2.opensuit.xmlmap.BindWithAnnotations'
11:51:49,309 INFO [STDOUT] 11:51:49,305 [INFO ] org.ow2.opensuit.core.impl.j2ee.OpenSuitServlet (OpenSuitServlet.java:100) - Initialized open SUIT '/WEB-INF/DemoApp.xml' successfully.
11:51:49,687 INFO [TomcatDeployment] deploy, ctxPath=/petals-webconsole-2.0.2, vfsUrl=petals-webconsole-2.0.2.war
11:51:49,718 WARN [config] Unable to process deployment descriptor for context '/petals-webconsole-2.0.2'
11:51:51,704 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=#petals-webconsole
11:51:51,714 ERROR [AbstractKernelController] Error installing to Start: name=persistence.unit:unitName=#petals-webconsole state=Create
java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a jta-data-source for a JTA enabled persistence context named: petals-webconsole
at org.jboss.jpa.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:115)
at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:285)
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:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
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)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:619)
11:51:51,919 INFO [TomcatDeployment] deploy, ctxPath=/petals-webconsole, vfsUrl=petals-webconsole.war
11:51:52,078 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** CONTEXTS IN ERROR: Name -> Error

persistence.unit:unitName=#petals-webconsole -> java.lang.RuntimeException: Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a jta-data-source for a JTA enabled persistence context named: petals-webconsole


11:51:52,093 INFO [Http11Protocol] D�marrage de Coyote HTTP/1.1 sur http-127.0.0.1-8080
11:51:52,171 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
11:51:52,287 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812041714)] Started in 44s:260ms


Anybody have an idea for this problem ?

Thank

best regards,

Adrien


SCJP 5, SCDJWS 5
http://adrien-ruffie.blogspot.com
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10210
    
166

Looks like the petals-webconsole-2.0.2.war has a persistence.xml which is causing this issue. Did you intentionally include that persistence.xml file? I ask this because, you said you were not using anything related persistence.

By the way, I would recommend that you move to AS 5.1.0. You are using 5.0.0 which had bugs and other issues which have been fixed in AS 5.1.0

[My Blog] [JavaRanch Journal]
Adrien Ruffie
Ranch Hand

Joined: Jan 14, 2009
Posts: 90
Thank Jaikiran for your response

No I haven't a persistence.xml in my webapp, but this problem can be

produced by one of my jar ?

activation-1.1.jar
cel-1.1-SNAPSHOT.jar
commons-jbi-0.9.2.jar
commons-lang-2.4.jar
commons-logging-1.0.4.jar
easywsdl-ext-wsdl4complexwsdl-2.1.jar
easywsdl-schema-2.1.jar
easywsdl-tool-xsd2xml-2.1.jar
easywsdl-wsdl-2.1.jar
geronimo-activation_1.1_spec-1.0.2.jar
geronimo-javamail_1.4_spec-1.5.jar
geronimo-servlet_2.5_spec-1.2.jar
jaxb-api-2.1.jar jaxb-impl-2.1.10.jar
jdom-1.1.jar opensuit-core-1.1-SNAPSHOT.jar
petals-jbi-1.0.2.jar petals-jmx-1.7-SNAPSHOT.jar
petals-jmx-api-1.3-SNAPSHOT.jar
petals-rmi-common-1.1.1.jar
petals-rmi-proxyclient-1.1.1.jar
petals-rmi-server-1.1.1.jar
runtime-0.4.1.5.jar
stax-api-1.0-2.jar xmlmap-annotations-1.0.jar
xmlmap-core-1.0.jar

And I can't move to AS 5.1.0 because, I have an explicit request for JBoss 5.0 ...

I'm really stuck
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5836
    
    7

You are going to have to dig through the JAR files and determine which one of them has persistence defined.


JBoss In Action
Adrien Ruffie
Ranch Hand

Joined: Jan 14, 2009
Posts: 90
Ok thank, this problem is corrected --> when I deployed my webapp from Eclipse, Eclipse automatically create META-INF/orm.xml and META-INF/persistence.xml ... Eclipse

but now I have another problem:

I provide a file available for example at:
http://192.168.1.108:8080/petals-webconsole/WebConsole/res/repository/components/petals-sample-clock-1.7.2-SNAPSHOT.zip

192.168.1.108 (it's my ip address)

but the file isn't available at http://192.168.1.108:8080/petals-webconsole/WebConsole/res/repository/components/petals-sample-clock-1.7.2-SNAPSHOT.zip

but when I try to access at : http://127.0.0.1:8080/petals-webconsole/WebConsole/res/repository/components/petals-sample-clock-1.7.2-SNAPSHOT.zip

the file is available !

Did you know where I can configure this ?

Best regards,
Adrien
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5836
    
    7

Does this help:
https://community.jboss.org/wiki/JBoss42FAQ
Adrien Ruffie
Ranch Hand

Joined: Jan 14, 2009
Posts: 90
Yes thank, I have found:

run.sh -b 192.168.1.108

allow to override the host or ip address used by jboss services

--> community.jboss.org/docs/DOC-10749

Best regars,

Adrien
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: JBoss persistence problem