[JBoss JIRA] (JASSIST-166) Invalid assumption involving "length" variable
by Flávio Brasil (JIRA)
Flávio Brasil created JASSIST-166:
-------------------------------------
Summary: Invalid assumption involving "length" variable
Key: JASSIST-166
URL: https://issues.jboss.org/browse/JASSIST-166
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA, 3.15.0-GA
Environment: MacBook Air
Mac OS X Lion 10.7.3 (11D50b)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
Reporter: Flávio Brasil
Assignee: Shigeru Chiba
Invalid assumption involving "length" variable. Method javassist.compiler.TypeChecker.atExpr(Expr) assumes that the variable length is a method from an array.
The problem is not reproductible with another variables names.
The main class to reproduce the bug is in the field "Steps to reproduce".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JGRP-1449) SEQUENCER race leads to lost messages
by David Hotham (JIRA)
David Hotham created JGRP-1449:
----------------------------------
Summary: SEQUENCER race leads to lost messages
Key: JGRP-1449
URL: https://issues.jboss.org/browse/JGRP-1449
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.9
Reporter: David Hotham
Assignee: Bela Ban
I'm seeing an issue where SEQUENCER is dropping messages, with logs like this:
2012-04-13 10:05:21.363 [Incoming-1,pisces,CFS-B-pisces-cfs02] ERROR org.jgroups.protocols.SEQUENCER - CFS-B-pisces-cfs02: non-coord; dropping FORWARD request from CFS-A-pisces-cfs03
It looks as though there's some sort of race where:
- a member ("CFS-B-pisces-cfs02") is becoming coordinator, but SEQUENCER hasn't yet seen the view change
- meanwhile some other member ("CFS-A-pisces-cfs03") has been told of the view change, and so SEQUENCER there forwards messages to the new coordinator
- but because the new coordinator doesn't yet know that it is coordinator, we hit the problem above.
The messages don't ever get retransmitted; so they're simply lost.
Here's some trace from the member who drops the message, with the line from my application showing that he does indeed become coordinator a few milliseconds later:
2012-04-13 10:05:21.363 [Incoming-1,pisces,CFS-B-pisces-cfs02] ERROR org.jgroups.protocols.SEQUENCER - CFS-B-pisces-cfs02: non-coord; dropping FORWARD request from CFS-A-pisces-cfs03
2012-04-13 10:05:21.393 [Incoming-2,pisces,CFS-B-pisces-cfs02] INFO c.m.c.CommunicatorComponent$Communicator - New view: MergeView::[CFS-B-pisces-cfs02|86] [CFS-B-pisces-cfs02, CFS-B-pisces-cfs03, CFS-A-pisces-cfs03, CFS-A-pisces-cfs02], subgroups=[CFS-A-pisces-cfs03|84] [CFS-A-pisces-cfs03, CFS-A-pisces-cfs02], [CFS-B-pisces-cfs03|85] [CFS-B-pisces-cfs03, CFS-A-pisces-cfs02, CFS-B-pisces-cfs02]
And here's trace from the other end, showing that message being broadcast in the new view.
2012-04-13 10:05:21.359 [Incoming-1,pisces,CFS-A-pisces-cfs03] INFO c.m.c.CommunicatorComponent$Communicator - New view: MergeView::[CFS-B-pisces-cfs02|86] [CFS-B-pisces-cfs02, CFS-B-pisces-cfs03, CFS-A-pisces-cfs03, CFS-A-pisces-cfs02], subgroups=[CFS-A-pisces-cfs03|84] [CFS-A-pisces-cfs03, CFS-A-pisces-cfs02], [CFS-B-pisces-cfs03|85] [CFS-B-pisces-cfs03, CFS-A-pisces-cfs02, CFS-B-pisces-cfs02]
2012-04-13 10:05:21.361 [ForkJoinPool-1-worker-0] INFO c.m.c.CommunicatorComponent$Communicator - Broadcasting ClusterMgmtMsg
I can try to get lower level trace from JGroups if that would help.
I'm using the same stack as in JGRP-1443.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-4787) CLONE - Host controller hangs intermitentlly when connecting to domain controller
by Emanuel Muckenhuber (JIRA)
[ https://issues.jboss.org/browse/AS7-4787?page=com.atlassian.jira.plugin.s... ]
Emanuel Muckenhuber resolved AS7-4787.
--------------------------------------
Resolution: Cannot Reproduce Bug
> CLONE - Host controller hangs intermitentlly when connecting to domain controller
> ---------------------------------------------------------------------------------
>
> Key: AS7-4787
> URL: https://issues.jboss.org/browse/AS7-4787
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Dominik Pospisil
> Assignee: Emanuel Muckenhuber
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> Host controller hangs intermittently when connecting to domain controller. Host controller is stuck forever and never recovers from this sistuation.
> I have never experienced this on local network, however this is pretty easy to reproduce using wireless network. The testing was done on private local wireless network with zero packet outages:
> 6973 packets transmitted, 6969 received, 0% packet loss, time 25334ms
> rtt min/avg/max/mdev = 1.398/4.318/284.480/11.672 ms, pipe 15, ipg/ewma 3.633/2.775 ms
> Also, the problem seems to be affecting only connecting - once the connection is made, all the management operations are performed correctly without problems.
> Logs from connecting hc:
> 14:37:01,827 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA-redhat-1
> 14:37:01,973 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 14:37:03,957 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA-redhat-1
> [Host Controller] 14:37:04,280 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA-redhat-1
> [Host Controller] 14:37:04,674 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.1.Final-redhat-1) starting
> [Host Controller] 14:37:05,919 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.3.GA-redhat-1
> [Host Controller] 14:37:05,943 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.3.GA-redhat-1
> [Host Controller] 14:37:05,963 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.4.GA-redhat-1
> [Host Controller] 14:37:06,018 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 192.168.1.67:9999
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-4787) CLONE - Host controller hangs intermitentlly when connecting to domain controller
by Emanuel Muckenhuber (JIRA)
[ https://issues.jboss.org/browse/AS7-4787?page=com.atlassian.jira.plugin.s... ]
Emanuel Muckenhuber closed AS7-4787.
------------------------------------
> CLONE - Host controller hangs intermitentlly when connecting to domain controller
> ---------------------------------------------------------------------------------
>
> Key: AS7-4787
> URL: https://issues.jboss.org/browse/AS7-4787
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Dominik Pospisil
> Assignee: Emanuel Muckenhuber
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> Host controller hangs intermittently when connecting to domain controller. Host controller is stuck forever and never recovers from this sistuation.
> I have never experienced this on local network, however this is pretty easy to reproduce using wireless network. The testing was done on private local wireless network with zero packet outages:
> 6973 packets transmitted, 6969 received, 0% packet loss, time 25334ms
> rtt min/avg/max/mdev = 1.398/4.318/284.480/11.672 ms, pipe 15, ipg/ewma 3.633/2.775 ms
> Also, the problem seems to be affecting only connecting - once the connection is made, all the management operations are performed correctly without problems.
> Logs from connecting hc:
> 14:37:01,827 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA-redhat-1
> 14:37:01,973 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 14:37:03,957 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.2.GA-redhat-1
> [Host Controller] 14:37:04,280 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA-redhat-1
> [Host Controller] 14:37:04,674 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.1.Final-redhat-1) starting
> [Host Controller] 14:37:05,919 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.3.GA-redhat-1
> [Host Controller] 14:37:05,943 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.3.GA-redhat-1
> [Host Controller] 14:37:05,963 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.4.GA-redhat-1
> [Host Controller] 14:37:06,018 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 192.168.1.67:9999
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-4910) Error deploy .EAR with. jar with relative paths on file MANIFEST.MF
by Roberto Requena (JIRA)
Roberto Requena created AS7-4910:
------------------------------------
Summary: Error deploy .EAR with. jar with relative paths on file MANIFEST.MF
Key: AS7-4910
URL: https://issues.jboss.org/browse/AS7-4910
Project: Application Server 7
Issue Type: Bug
Components: EJB, Web
Affects Versions: 7.1.1.Final
Environment: Software
Linux debian 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)
Eclipse Java EE IDE for Web Developers.
Version: Indigo Service Release 1
Build id: 20110916-0149
JBoss Tools 3.3 (Indigo)
Hardware
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
stepping : 11
cpu MHz : 2660.399
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3
cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5320.79
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
stepping : 11
cpu MHz : 2660.399
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
Reporter: Roberto Requena
Assignee: jaikiran pai
When I try to deploy a .EAR project on the server with the following files "juh-3.2.1.jar" and "jurt-3.2.1.jar" contained in the web project lib folder, the server displays the following error:
{noformat}
WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
09:31:13,183 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
09:31:13,424 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
09:31:13,498 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
09:31:14,836 INFO [org.xnio] XNIO Version 3.0.3.GA
09:31:14,849 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
09:31:14,860 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
09:31:14,879 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
09:31:14,950 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
09:31:14,970 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
09:31:15,010 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
09:31:15,062 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
09:31:15,082 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
09:31:15,106 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
09:31:15,156 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
09:31:15,178 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
09:31:15,190 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
09:31:15,217 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
09:31:15,231 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
09:31:15,259 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
09:31:15,531 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
09:31:15,582 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Arrancando Coyote HTTP/1.1 en puerto http--127.0.0.1-8080
09:31:16,144 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
09:31:16,306 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
09:31:16,308 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
09:31:16,325 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment TestDeploy.ear
09:31:16,329 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments
09:31:16,342 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015002: Deployment of 'Download.war' requested, but the deployment is not present
09:31:16,343 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found Prueba-ear.ear in deployment directory. To trigger deployment create a file called Prueba-ear.ear.dodeploy
09:31:16,344 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TestDeploy.ear in deployment directory. To trigger deployment create a file called TestDeploy.ear.dodeploy
09:31:16,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "Prueba-ear.ear"
09:31:16,629 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "TestDeploy.ear"
09:31:16,690 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "TestDeployWeb.war"
09:31:16,722 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Prueba-ejb-0.0.1-SNAPSHOT.jar"
09:31:16,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Prueba-web-0.0.1-SNAPSHOT.war"
09:31:16,857 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry ridl.jar in "/usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments/TestDeploy.ear/TestDeployWeb.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
09:31:16,858 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jurt.jar in "/usr/local/org.jboss/as/versions/jboss-as-7.1.1.Final/standalone/deployments/TestDeploy.ear/TestDeployWeb.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference.
09:31:16,871 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: Failed to process phase STRUCTURE of subdeployment "TestDeployWeb.war" of deployment "TestDeploy.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.createAdditionalModule(ManifestClassPathProcessor.java:193) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.handlingExistingClassPathEntry(ManifestClassPathProcessor.java:185) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:162) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
09:31:17,113 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for primary
09:31:17,188 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment Prueba-ear.ear
09:31:17,272 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment Prueba-ejb-0.0.1-SNAPSHOT.jar
09:31:17,274 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment Prueba-web-0.0.1-SNAPSHOT.war
09:31:17,287 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named MemberRegistration in deployment unit subdeployment "Prueba-ejb-0.0.1-SNAPSHOT.jar" of deployment "Prueba-ear.ear" are as follows:
java:global/Prueba-ear/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.prueba.controller.MemberRegistration
java:app/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.prueba.controller.MemberRegistration
java:module/MemberRegistration!org.prueba.controller.MemberRegistration
java:global/Prueba-ear/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration
java:app/Prueba-ejb-0.0.1-SNAPSHOT/MemberRegistration
java:module/MemberRegistration
09:31:17,310 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016005: Starting Services for CDI deployment: Prueba-ear.ear
09:31:17,343 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900 1.1.5 (AS71)
09:31:17,631 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011402: Starting Persistence Unit Service 'Prueba-ear.ear/Prueba-ejb-0.0.1-SNAPSHOT.jar#primary'
09:31:17,766 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-2) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
09:31:17,777 INFO [org.hibernate.Version] (MSC service thread 1-2) HHH000412: Hibernate Core {4.0.1.Final}
09:31:17,779 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000206: hibernate.properties not found
09:31:17,792 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000021: Bytecode provider name : javassist
09:31:17,809 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-2) HHH000204: Processing PersistenceUnitInfo [
name: primary
...]
09:31:17,963 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-2) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
09:31:18,282 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-2) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
09:31:18,287 WARN [org.hibernate.dialect.H2Dialect] (MSC service thread 1-2) HHH000431: Unable to determine H2 database version, certain features may not work
09:31:18,290 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-2) HHH000423: Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
09:31:18,300 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-2) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
09:31:18,304 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-2) HHH000397: Using ASTQueryTranslatorFactory
09:31:18,377 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-2) Hibernate Validator 4.2.0.Final
09:31:18,689 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000227: Running hbm2ddl schema export
09:31:18,703 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000389: Unsuccessful: drop sequence hibernate_sequence
09:31:18,704 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) Sequence "HIBERNATE_SEQUENCE" no encontrado
Sequence "HIBERNATE_SEQUENCE" not found; SQL statement:
drop sequence hibernate_sequence [90036-161]
09:31:18,708 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-2) HHH000230: Schema export complete
09:31:18,732 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment Prueba-ear.ear
09:31:19,130 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Inicializando Mojarra 2.1.7-jbossorg-1 (20120227-1401) para el contexto '/Prueba-web'
09:31:20,124 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /Prueba-web
09:31:20,133 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990
09:31:20,133 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 7241ms - Started 243 of 326 services (2 services failed or missing dependencies, 80 services are passive or on-demand)
09:31:20,334 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "Prueba-ear.ear" was rolled back with no failure message
09:31:20,335 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TestDeploy.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE: Failed to process phase STRUCTURE of subdeployment \"TestDeployWeb.war\" of deployment \"TestDeploy.ear\""}}
09:31:20,355 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment TestDeployWeb.war in 19ms
09:31:20,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment TestDeploy.ear in 29ms
09:31:20,372 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment Prueba-ear.ear
09:31:20,381 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'Prueba-ear.ear/Prueba-ejb-0.0.1-SNAPSHOT.jar#primary'
09:31:20,382 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000227: Running hbm2ddl schema export
09:31:20,386 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000230: Schema export complete
09:31:20,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment Prueba-ejb-0.0.1-SNAPSHOT.jar in 63ms
09:31:20,399 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment Prueba-web-0.0.1-SNAPSHOT.war in 64ms
09:31:20,402 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment Prueba-ear.ear in 67ms
09:31:20,403 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestDeploy.ear"."TestDeployWeb.war".STRUCTURE: Failed to process phase STRUCTURE of subdeployment "TestDeployWeb.war" of deployment "TestDeploy.ear"
09:31:20,406 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TestDeploy.ear\".\"TestDeployWeb.war\".STRUCTURE: Failed to process phase STRUCTURE of subdeployment \"TestDeployWeb.war\" of deployment \"TestDeploy.ear\""}}}}
09:31:20,407 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
{noformat}
I could see that causing the error are claspath declared in MANIFEST.MF files of these .jar files because they contain relative paths.
{noformat}
juh-3.2.1.jar
Manifest-Version: 1.0
Class-Path: ridl.jar jurt.jar ../../lib/ ../bin/
{noformat}
{noformat}
jurt-3.2.1.jar
Manifest-Version: 1.0
Class-Path: ridl.jar unoloader.jar ../../lib/ ../bin/
{noformat}
Also I could see two things:
# When I deploy only the Web project on the server containing these .jar files the error does not occur.
# And If I remove the contents of the MANIFEST.MF file and deploying the .ear project the error does not occur.
I have a .EAR project for test that demonstrates the error, but did not see any option to attach files. If you wish, tell me how to send them.
Any other thing that I can help to order. I want to use to thank Stephen Coy and Tomaz Cerar for help.
Thanks and sorry for my English
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-4952) Calling wasCancelCalled() method on SessionContext in a bussiness method of a bean throws IllegalStateException for method being called remotely
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-4952?page=com.atlassian.jira.plugin.s... ]
jaikiran pai commented on AS7-4952:
-----------------------------------
The real issue here is EJBCLIENT-42. I have fixed that part and sent a pull request for that project. Once it's reviewed and merged, we'll need a release of that library and also the corresponding server side implementation to handle the cancel request from the remote client https://github.com/jaikiran/jboss-as/commit/c3b77801e11ada324adb6b3bb9e85.... I'll send a separate pull request for server side once the EJB client version is released.
> Calling wasCancelCalled() method on SessionContext in a bussiness method of a bean throws IllegalStateException for method being called remotely
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4952
> URL: https://issues.jboss.org/browse/AS7-4952
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB, Remoting
> Reporter: Ondřej Chaloupka
> Assignee: jaikiran pai
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> It seems there is still a problem on calling asynchronous method with remote client. When wasCancelCalled() method is invoked (from SessionContext) inside of the asynchronous method then you get IllegalStateException (JBAS014379: No asynchronous invocation in progress) instead of a true/false value when the method is asynchronously called actually.
> {code}
> ERROR [org.jboss.as.ejb3.invocation] (EJB default - 10) JBAS014134: EJB Invocation failed on component AsyncBean for method public abstract java.util.concurrent.Future org.jboss.as.test.integration.ejb.async.AsyncBeanCancelRemoteInterface.asyncRemoteCancelMethod() throws java.lang.InterruptedException: javax.ejb.EJBException: java.lang.IllegalStateException: JBAS014379: No asynchronous invocation in progress
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:165) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:229) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:303) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:189) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:80) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:42) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:43) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:297) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:67) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:199) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_23]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_23]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_23]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.IllegalStateException: JBAS014379: No asynchronous invocation in progress
> at org.jboss.as.ejb3.context.SessionContextImpl.wasCancelCalled(SessionContextImpl.java:106) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.test.integration.ejb.async.AsyncBean.asyncRemoteCancelMethod(AsyncBean.java:92) [AsyncTestCase.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_23]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_23]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_23]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_23]
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:374) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:129) [jboss-as-weld-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:137) [jboss-as-weld-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:94) [jboss-as-weld-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:227) [jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> ... 29 more
> {code}
> The test could be fine here:
> https://github.com/ochaloup/jboss-as/blob/async-method-cancel-invocation/...
> and the invocation of the wasCancelCalled method is here:
> https://github.com/ochaloup/jboss-as/blob/async-method-cancel-invocation/...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBRULES-3530) The drools-planner-benchmark artifact should not depend on itext
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created JBRULES-3530:
-----------------------------------------
Summary: The drools-planner-benchmark artifact should not depend on itext
Key: JBRULES-3530
URL: https://issues.jboss.org/browse/JBRULES-3530
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Optional
itext is pdf stuff, which we don't need normally. Furthermore, the itext jar has a MANIFEST.mf classpath entry that leads to an unexisting itext-toolbox jar.
{code}
[INFO] +- org.drools.planner:drools-planner-benchmark:jar:5.5.0-SNAPSHOT:compile
[INFO] | +- org.jfree:jfreechart:jar:1.0.14:compile
[INFO] | | +- org.jfree:jcommon:jar:1.0.17:compile
[INFO] | | +- xml-apis:xml-apis:jar:1.3.04:compile
[INFO] | | \- com.lowagie:itext:jar:2.1.2:compile (version managed from 2.1.5)
[INFO] | | +- bouncycastle:bcmail-jdk14:jar:138:compile
[INFO] | | \- bouncycastle:bcprov-jdk14:jar:138:compile
[INFO] | \- org.freemarker:freemarker:jar:2.3.19:compile
{code}
Which results in to this warn messages when deploying drools-planner-webexamples to jboss:
{code}
2012/06/06 02:35:48,584 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "droolsplanner.war"
2012/06/06 02:35:48,665 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "ROOT.war"
2012/06/06 02:35:51,780 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context:
2012/06/06 02:36:00,799 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry iText-toolbox.jar in "/content/droolsplanner.war/WEB-INF lib/itext-2.1.2.jar" does not point to a valid jar for a Class-Path reference.
2012/06/06 02:36:00,879 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry iText-toolbox-2.1.2.jar in "/content/droolsplanner.war/WEB-INF/lib/itext-2.1.2.jar" does not point to a valid jar for a Class-Path reference.
2012/06/06 02:36:01,070 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
2012/06/06 02:36:02,620 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /droolsplanner
2012/06/06 02:36:06,433 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "droolsplanner.war"
2012/06/06 02:36:06,608 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "ROOT.war"
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months