Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348949

Summary:

Malformed fragment bundle doesn't output any logging

Product:

[RT] Virgo

Reporter:

Jochen Szostek <jochen.szostek>

Component:

runtime

Assignee:

Project Inbox <virgo-inbox>

Status:

CLOSED WORKSFORME

QA Contact:

Severity:

minor

Priority:

CC:

eclipse, glyn.normington, hsiliev

Version:

3.0.0.M05

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
(malformed) fragment that doens't show any logging output	none

Description Jochen Szostek

2011-06-09 15:27:58 EDT

Created attachment 197724 [details]
(malformed) fragment that doens't show any logging output

I created a fragment bundle and it doesn't show any output when deploying via SpringSource Tool Suite.

Forum post:
http://www.eclipse.org/forums/index.php/m/677249/#msg_677249

Logging output when dropped into pickup folder:

[2011-06-09 21:25:20.129] INFO  fs-watcher                   org.eclipse.virgo.medic.eventlog.default                         HD0001I Hot deployer processing 'CREATED' event for file 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT.jar'.
[2011-06-09 21:25:20.130] INFO  fs-watcher                   o.e.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener     ApplicationDeploying path 'D:\dev\server\virgo-tomcat-server-3.0.0.M05\pickup\org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT.jar'.
[2011-06-09 21:25:20.189] INFO  fs-watcher                   o.e.v.k.m.i.deployer.ModelInstallArtifactLifecycleListener        Processing installing event for bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT' version '0.0.0'
[2011-06-09 21:25:20.193] INFO  fs-watcher                   org.eclipse.virgo.medic.eventlog.default                         DE0000I Installing bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT' version '0.0.0'.
[2011-06-09 21:25:20.196] INFO  fs-watcher                   o.e.virgo.kernel.userregion.internal.quasi.DependencyCalculator   Calculating missing dependencies of bundle(s) 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0'
[2011-06-09 21:25:20.201] INFO  fs-watcher                   o.e.virgo.kernel.userregion.internal.quasi.DependencyCalculator   The dependencies of '[org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]' are '[]'
[2011-06-09 21:25:20.203] INFO  fs-watcher                   o.eclipse.virgo.kernel.model.internal.bundle.ModelBundleListener  Processing installed event for bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT:0.0.0' in region 'org.eclipse.virgo.region.user'
[2011-06-09 21:25:20.205] INFO  fs-watcher                   org.eclipse.virgo.medic.eventlog.default                         DE0001I Installed bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT' version '0.0.0'.
[2011-06-09 21:25:20.205] INFO  fs-watcher                   o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]' popped and set to 'BundleDelegatingClassLoader for [Virgo Kernel Deploy
er (org.eclipse.virgo.kernel.deployer)]'
[2011-06-09 21:25:20.208] INFO  fs-watcher                   o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]' pushed and set to 'KernelBundleClassLoader: [bundle=org.springframework
.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]'
[2011-06-09 21:25:20.208] INFO  fs-watcher                   o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'KernelBundleClassLoader: [bundle=org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]' popped and set to 'BundleDelegatingClassLoader for [Virgo Kernel D
eployer (org.eclipse.virgo.kernel.deployer)]'
[2011-06-09 21:25:20.211] INFO  fs-watcher                   o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'BundleDelegatingClassLoader for [Virgo Kernel Deployer (org.eclipse.virgo.kernel.deployer)]' pushed and set to 'KernelBundleClassLoader: [bundle=org.springframework
.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]'
[2011-06-09 21:25:20.211] INFO  fs-watcher                   o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'KernelBundleClassLoader: [bundle=org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]' pushed and set to 'KernelBundleClassLoader: [bundle=org.springfram
ework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]'
[2011-06-09 21:25:20.212] INFO  fs-watcher                   org.eclipse.virgo.kernel.core.internal.BundleStartTracker         Adding signal 'org.eclipse.virgo.kernel.install.artifact.internal.AbstractInstallArtifact$StateMonitorSignal@273e07bd' for bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0
 [103]'
[2011-06-09 21:25:20.212] INFO  fs-watcher                   o.e.v.k.i.a.internal.AtomicInstallArtifactLifecycleListener       No atomic parent of bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT' version '0.0.0' in scope 'null' to propagate starting event to
[2011-06-09 21:25:20.213] INFO  fs-watcher                   org.eclipse.virgo.medic.eventlog.default                         DE0004I Starting bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT' version '0.0.0'.
[2011-06-09 21:25:20.213] INFO  fs-watcher                   org.eclipse.virgo.kernel.core.internal.BundleStartTracker         Non-Spring DM powered bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0 [103]' has started. Driving signals '[org.eclipse.virgo.kernel.install.artifact.internal.AbstractIns
tallArtifact$StateMonitorSignal@273e07bd]'.
[2011-06-09 21:25:20.214] INFO  start-signalling-5           org.eclipse.virgo.kernel.core.internal.BundleStartTracker         Driving signal 'org.eclipse.virgo.kernel.install.artifact.internal.AbstractInstallArtifact$StateMonitorSignal@273e07bd'
[2011-06-09 21:25:20.214] INFO  fs-watcher                   o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'KernelBundleClassLoader: [bundle=org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]' popped and set to 'KernelBundleClassLoader: [bundle=org.springfram
ework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]'
[2011-06-09 21:25:20.214] INFO  start-signalling-5           o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'KernelBundleClassLoader: [bundle=org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]' pushed and set to 'KernelBundleClassLoader: [bundle=org.springfram
ework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]'
[2011-06-09 21:25:20.215] INFO  fs-watcher                   o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'KernelBundleClassLoader: [bundle=org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]' popped and set to 'BundleDelegatingClassLoader for [Virgo Kernel D
eployer (org.eclipse.virgo.kernel.deployer)]'
[2011-06-09 21:25:20.216] INFO  start-signalling-5           org.eclipse.virgo.medic.eventlog.default                         DE0005I Started bundle 'org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT' version '0.0.0'.
[2011-06-09 21:25:20.216] INFO  start-signalling-5           o.e.v.k.i.artifact.internal.bundle.BundleThreadContextManager     Thread context class loader 'KernelBundleClassLoader: [bundle=org.springframework.orm_3.0.5.RELEASE_fix-0.0.1-SNAPSHOT_0.0.0]' popped and set to 'KernelBundleClassLoader: [bundle=org.springfram

Comment 1 Hristo Iliev

2011-06-10 08:02:43 EDT

The attached fragment does not seem to have any useful manifest entries.

Deploying the attached JAR simply outputs start logs, but replacing the manifest with the one from the thread brings a lot of exceptions in the logs. 

Can you please check if the build you use updates the manifest and attach a new JAR that reproduces the problem?

Comment 2 Glyn Normington

2011-06-27 06:21:26 EDT

Closing as unreproducible until we get a bundle to reproduce,